Skip to content
opsinjs
Edit this page

opsinjs

Health

What opsinjs decides, what your product decides, and the ten rules every health screen must pass.

opsinjs decides how health information is presented. It never decides what that information means. No component has had an independent accessibility review or any clinical review, and nothing here is for a production health surface.

The ten rules

Check each on the rendered screen before merging anything that shows, interprets or collects health data.

  1. Never carry clinical status in colour alone. Two colour axes
  2. Never mix the category axis with the status axis on one element. Two colour axes
  3. Never use "normal" or "abnormal" about a person's own result. Reference ranges
  4. Never show a number without its unit, its scale and when it was measured. Numbers and units
  5. Never show more digits than the measurement supports. Numbers and units
  6. Never draw a trend from fewer points than the metric's minimum window. Trends and uncertainty
  7. Never put more than one urgent surface on a screen. Alerts
  8. Never convey urgency with motion, sound or haptics alone. Alerts
  9. Never present a result without saying what, if anything, to do, even when the answer is "nothing". High-stakes moments
  10. Never collect health data without saying what it is for and how to stop. Consent and privacy

To break a rule, record which, why, who agreed and the compensating control. Lint rules for rules 2, 3 and 4 are planned, not written, so all ten are human checks today. Safety review holds the checklist.

Who this is for

Someone with no clinical training, reading their own result on their own phone with nobody to ask. New to the unit, they give the screen 3 to 15 seconds. Months later they want only the figure, from the same screen.

  1. Expand every clinical term in place on first encounter, with Term.
  2. Give every value its scale, its unit and a sentence on what it means.
  3. Treat a four-year-old phone, low brightness, the largest text size, reduced motion, reduced transparency, increased contrast and greyscale as the expected case. Never fix the height of a card holding a clinical sentence.
  4. Never carry anything important once, quickly, or on a single channel.
  5. Order a result as value, meaning, then next step.

Scope and safety

opsinjs renders decisions. It does not make them. It never triages, diagnoses or advises, and it is not a medical device. Every clinical judgement on screen originates outside opsinjs, where your organisation can name, review, version and audit it.

  1. No component derives a clinical status from a value. There is no threshold prop and there will not be one, because your product owns every threshold. Pass status in from one mapping your clinical owner approved, versioned and tested at its boundaries, never from code in or beside a component.
  2. No component supplies a reference range. Ranges arrive with their source, and whoever issued one owns it.
  3. No component's wording asserts a clinical meaning. Your clinical content owner writes that sentence.
  4. No component escalates on its own.

You are responsible for every clinical claim your interface makes, including the ones made by colour, icon, order and emphasis rather than by words. Your organisation and its regulator decide whether your product is a medical device.

DisclaimerNote, ConsentSheet, AlertBanner and CareCard are not compliance controls, and a disclaimer is necessary and insufficient. Keep a visible route to a human wherever a reader may be frightened, even offline or with the value missing. No component notices distress. If DCB0129 or DCB0160 apply, they apply whole, and opsinjs produces no hazard log or clinical safety case report. Nothing here is legal advice.

Evidence

Each instrument is named, not paraphrased, because a design system's summary of a regulation is a second-hand reading of a text you must legally read directly. Confirm the current version of each, because they are amended.

  • Regulation (EU) 2017/745 (the Medical Device Regulation, "MDR") is the EU framework under which software may itself qualify as a medical device.
  • MDCG 2019-11 is the Medical Device Coordination Group guidance on qualification and classification of software under MDR and IVDR.
  • IMDRF, "Software as a Medical Device (SaMD): Key Definitions" is the international definition the term SaMD comes from, and the vocabulary most regulators build on.
  • DCB0129, "Clinical Risk Management: its Application in the Manufacture of Health IT Systems" is the NHS England information standard placing clinical risk-management obligations on the manufacturer of health IT.
  • DCB0160, "Clinical Risk Management: its Application in the Deployment and Use of Health IT Systems" is the companion standard, placing obligations on the deploying organisation.
  • WCAG 2.2 (W3C Recommendation) is the accessibility standard opsinjs measures itself against; see Accessibility. Success criteria 1.4.1 (Use of Colour) and 2.2.2 (Pause, Stop, Hide) are the normative basis for rules 1 and 8.
  • The systematic review of laboratory-result presentation formats in JMIR (2024), 10.2196/53993, anchors rules 3, 4 and 5 in the claim that a number needs a scale, not in any visual treatment.
  • The patient-portal presentation study in BMC Medical Informatics and Decision Making (2018), 10.1186/s12911-018-0589-7, is cited for the same claim.

Rules 2, 6, 7, 9 and 10 are opinion, as are the audience model and the position that no component derives severity from a value.

Not written yet. External clinical review of the whole Health section. Until it happens, no page here may be described as clinically approved.