Patterns
Sharing with a clinician
Export and hand-off surfaces a clinician can read in ninety seconds, without the product implying it has interpreted anything.
The export answers to the clinician, who wants the fewest facts that change a decision. The screen before it answers to the reader.
When to use it
Use it when the reader takes their logs to an appointment, a clinic asks for readings between visits, or a referral needs their history.
Do not use it for:
- Continuous clinical monitoring, a regulated surface with alerting obligations that opsinjs is not built for. See Safety review.
- Sharing with a family member or carer, which needs its own design.
- Raw data portability, which is a different artefact. Offer both.
- Granting and revoking access. That is Consent and permissions.
How it works
- The reader picks a window and the measures to include. With nothing to share, say what would be needed rather than producing an empty document.
- The preview is the artefact itself, and the reader can still change the dates or remove a measure.
- In person, the product prints a one-page summary that depends on no colour.
- Sending needs consent naming the recipient, scope and duration, and a record of what was sent, to whom and when.
- The reader sees what was shared, to whom and until when. Expiry is visible, and revoking is immediate and says what the recipient may already hold.
The export itself:
- Fits one page, and the first third is the answer: identity, window, measures included and a summary sentence.
- States values, ranges and dates, never the product's status words. Those are written for a layperson and would read as a clinical assessment.
- Declares completeness: "42 of a possible 60 mornings, none between 12 and 19 August." Gaps are declared, never filled.
- Carries provenance: which device, which method, and whether each value was measured or self-entered.
- Marks each stale value, as in Offline and stale data.
Components
opsinjs ships no export or summary component. The product builds the document from these:
- Table carries each chart's table twin into the export.
- Value and RelativeTime format every number and date.
- ConsentSheet asks before anything is sent.
- DisclaimerNote says what the document is, because it will outlive the app.
Content
- Write the export for the clinician: "Home blood pressure, 3 May to 2 June 2026. 42 morning readings of a possible 60. Self-measured, upper-arm cuff." Never "your amazing progress".
- Write the screen for the reader: "This is what Dr Ellis will see. You can change the dates or remove a metric before sending."
Accessibility
- The export is a document, not a screenshot: real text, real headings, real tables.
- Nothing in it depends on colour, because it will be printed in monochrome and photocopied.
- The share control names the recipient: "Send summary to Dr Ellis's clinic", not "Send".
- Test the print styles: page breaks between sections, and URLs printed where link text is not self-describing.