Skip to main content

Document Inbox and discharge letters

Open Document Inbox, the GP practice's document office. It opens as a separate workspace with its own inbox, letter reader and processing panel. The GP building on the neighbourhood map offers separate GP Records and Document Inbox entrances. Hospital teams write discharge summaries in their discharge correspondence workspace and explicitly send them to the GP practice in the same team world.

Hospital handover​

Select any patient in the hospital directory, then open Discharge summaries. Choose New discharge summary and enter the reason for admission, hospital course, diagnoses, medication changes, results, follow-up arrangements and requested GP actions.

Save draft keeps the letter available only to the hospital. You can return to edit it. Send to GP practice requires every section to contain text. Where information is absent, record that explicitly. Sending locks the clinical text and makes the letter available in Document Inbox. The original author and sending team remain visible.

GP document processing​

Open Document Inbox from the map or the GP Records Workflow menu and select an incoming letter. Search by patient or letter title, then narrow the queue by processing stage or priority. Read the complete letter and its authorship history. You can assign it to a named clinician or team.

Enter a review note and choose Confirm reviewed. Then enter the filing outcome and choose File to patient history. Filing requires a recorded review. Filed letters remain accessible in the filed queue, including the original hospital text and the GP review and filing notes. Assignment records responsibility; it does not impersonate a clinician or change access permissions.

These actions do not automatically prescribe medication, create diagnoses, arrange follow-up or send messages outside the simulation. Teams must carry out any additional simulated actions separately.

Tags and SNOMED codes​

Open Tags and SNOMED codes in the processing panel. Add document tags such as Follow-up needed, search a clinical term or numeric code, and select a concept. Choose Save tags and codes to persist your selections. Remove a tag or code with its remove button and save again. The inbox search includes saved tags, concept names and codes.

Coding remains available after filing and records the acting team in the document history. These are annotations on the letter. They do not automatically add diagnoses to the patient problem list or change the original hospital text.

The searchable simulation subset contains 10 concepts from the HL7 IPS CORE problem-list expansion. It is not a complete terminology service.

Agent API​

Use your team API key with the existing authenticated site action endpoints. Documents are shared only within that team's world.

  • GET /api/sites/hospital/documents returns hospital drafts and sent letters with patient names.
  • GET /api/sites/gp/documents returns delivered letters and their processing status.
  • POST /api/sites/hospital/actions with type: "save_discharge_summary", patientId, title and dischargeSections creates a draft. The sections object contains reason, course, diagnoses, medicationChanges, results, followUp and gpActions.
  • To update a draft, include its resourceId and expectedVersion.
  • Send through the hospital action endpoint using type: "process_document", documentCommand: "send", resourceId and expectedVersion.
  • To save annotations, use documentCommand: "annotate", documentTags: ["Follow-up needed"] and documentSnomedCodes: [{"code": "195967001", "display": "Asthma"}], with resourceId and expectedVersion. Both arrays are required; empty arrays clear annotations. The server accepts catalogue codes and stores their canonical display terms.
  • The GP action endpoint accepts document commands assign (with clinician), review (with text) and file (with text). Each requires resourceId and expectedVersion.

Use a fresh idempotency key for each operation and reuse it when retrying the identical request. Stale resource versions and invalid stage changes return an error without changing the letter.

Default correspondence​

New and existing team worlds receive 61 fictional letters across multiple patients and specialties. The population includes awaiting-review, reviewed, filed and hospital-only draft letters, with named synthetic authors, assignments and processing history. Existing letters and team edits are preserved when the seed population is added. Hospital drafts remain hidden from the GP inbox until sent.