> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/use-cases/resilient-health-supply.md). # Resilient healthcare supply Sourcing prequalified medicines across borders with end-to-end traceability — a resilient health-supply network on NFH fabric. A public-hospital procurement officer in Lagos needs to source generic medicines from suppliers across West Africa. Today that means fragmented supplier lists, prequalification checks done by email, and traceability that regulators ask for but no one can produce quickly. A single counterfeit or out-of-spec batch is a patient-safety event and a compliance failure at once. NFH fabric lets health buyers **discover prequalified suppliers, verify quality claims cryptographically, and carry a batch's provenance from manufacture to shelf** — across borders, without a central intermediary owning the data. ## What changes * Prequalification becomes a **verifiable credential checked in milliseconds**, not an email chain — expired or revoked status is caught before the order, not after. * A pharmacist or nurse can **confirm a batch is genuine and in-date** by verifying its provenance credential at the point of dispensing. * Traceability for regulators is **produced automatically** from the anchored trail instead of reconstructed under audit pressure. * Smaller regional suppliers reach public buyers directly, **widening supply and resilience** against single-source shocks. * Procurement stays **within budget** with atomic settlement against delivery proof. ## Where to start Register two suppliers and one hospital in a sandbox. Issue a prequalification credential and a batch-provenance credential, publish a small formulary catalogue, and run one cross-border order with verification and the provenance trail anchored end-to-end. Review the trail with a compliance officer before widening the supplier set. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nfh.global/use-cases/resilient-health-supply.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.