Built by opsinjs
Showcase
Whole screens built only from opsinjs components. opsinjs built every one of them and every figure in them is invented. No opsinjs component has had an accessibility review or a clinical review, so no screen here is for a production health surface.
Diabetes medicines app
MedicinesA medicines diary that records what somebody takes and reminds them at times they chose. It calculates no dose, and it never marks a dose as missed.
35 components, among them DoseTracker, LogSheet, Stepper, Sheet, ConsentSheet, TimelineEntry, TabBar.
Patient record portal
Health recordsA patient's own view of the record their hospitals write, with who can see it, who looked, and a card a paramedic can read. It explains nothing it shows.
24 components, among them TabBar, RadioGroup, Switch, Accordion, SegmentedControl, Dialog, Sheet.
Results screen
Lab resultsOne example lab result, then what it means, the next step and its source, in screen reader order. It states one status and tints one title by category.
7 components, among them ResultCard, Term, CareCard, RelativeTime, DisclaimerNote, Surface.
Entries from other teams
None yet. An entry will have to clear four tests, published while there was nothing to put here so that nobody's first request set the bar.
| Test | What it means |
|---|---|
| A real product with real readers | Shipped and reachable by somebody who is not on the team. Concept work and internal demos belong somewhere else. |
| A named team who agreed to appear | Entries are opt in, attributed, and removed on request without discussion. |
| Screens with the colour axes intact | A product that themed opsinjs into one colour axis is welcome to, and it is not an example of this system working. |
| No patient data, ever | Screenshots use synthetic readings, because a plausible series beside a date and a place can identify somebody. |
Building something with opsinjs? Say so on GitHub. Until then, the patterns show the components working together one screen at a time.