The MyChartWriter-style clinical encounter: classify the visit (class + patient type) → document the clinical sections with an ambient AI scribe → point-of-care HCC panel (recapture/suspect, live RAF) → CMS-2021 E/M engine (MDM or time, with a why-this-level trace) → charge capture → sign. Signing files an immutable chart document (into the Document Center) and drops the visit into the work queue (incomplete / awaiting-sign / signed-unbilled) → superbill. encounter-service behind encounter:read/write/pre-authorize/sign.
Standard of work · ISO/IEC 25010 — Meets 9/9
- 1. Self-identifyingUsability — appropriateness recognizabilityThe page names itself: breadcrumb, title, section, status badge, and a page id.
- 2. Navigable forward & backUsability — operabilityBack/Next step through the product; breadcrumb + active sidebar; browser back works.
- 3. Demo-prefilled — no empty statesUsability — learnabilityEvery form is pre-filled with realistic demo data so the screen is never blank.
- 4. Accessible — AAA, large fonts, big targetsUsability — accessibilityLight mode, 7:1+ contrast, ≥44px controls — built for a 76-year-old physician.
- 5. Clear result feedbackFunctional suitability — appropriateness; Reliability — fault toleranceEvery action maps a Result to a visible success/error message; codes → HTTP status.
- 6. Secure by default + sign-outSecurity — confidentiality & authenticityDefault-deny permissions, practice-scoped data, a sign-out control, no PHI in logs.
- 7. ResponsivePortability / Compatibility — adaptabilityWorks on desktop, tablet, and phone; the sidebar collapses on narrow screens.
- 8. ResilientReliability — availability & recoverability; Performance efficiencyLoading and upstream-down states are handled — never a blank or frozen screen.
- 9. ConsistentMaintainability — modularity & reusabilityOne shell, one set of design tokens, shared components across every page.
Encounters
Worklist
No encounters yet. Open a new one above.
Select an encounter on the left, or open a new one.