Troubleshooting organised by what you see, not by error code
A new Troubleshooting section starts from the symptom in
front of you: the callback never arrives, everything returns 401, the OTP never arrives,
a call is accepted then nothing happens, a consent stays stuck in Requested. Each page
works through the checks in order and names what counts as proof the fix worked. The
Error codes reference now points here first for
anyone who has a symptom rather than a code.
A first fifteen minutes that needs nothing but a browser
Your first fifteen minutes gives you something to do while your sandbox registration is reviewed: one gateway session call transcribed from this repository's specification, and your own first call assembled with the credential placeholders named for where they come from. The transcribed request is read from the OpenAPI spec in this repository, not invented. The spec carries no captured response body, only the field list, and the page says plainly which parts are observed and which are not yet.
Going live, in order
Going live states the sandbox exit process in the order it runs: the demonstration, functional testing and the security audit, the exit form, and the second demonstration to the Health Tech Committee. It names what is not yet published rather than guessing it in.
Every doc page serves itself as markdown, for agents and people alike
Every documentation route now has a "Copy page as Markdown" and "View as Markdown" button,
and serves its own index.md alongside the rendered page. A repository-wide llms.txt and
llms-full.txt, plus one llms.txt per module, are built on every release so an agent can
retrieve exactly the page it needs without scraping HTML. See
Build with AI for the skills and the
Docs MCP server built on the same content.
Seven PHR operations renamed
Seven operations in the P1 through P3 and PHR application services references carried a stray " Copy" suffix. Each was checked against the operation its name implied it duplicated. None turned out to be a true duplicate: five have no other operation to duplicate, and the other two point at a different host or a different API entirely. Every one has been given a name that says what it does instead. The corrections log records the comparison.