rpms-ux

rpms-ux

The workflows we are rolling out on RPMS, from the people who do them to the screens they do them on. Everything here is built from files in this repo, so it is as current as the branch it was built from.

Where it stands

On YDB stack 0928 (build bcer-9.0-20260928-7e57c74-ydb), built 2026-11-10. Results and screenshots are per stack, so another stack's branch shows its own.

30 / 471scenarios passing, in results.tsv
139 / 139stories the analyst has not yet walked (fit unknown)
29 / 38journey steps on a screen that have its screenshot
13 / 44screens in the capture backlog captured
5 / 22backlog items done
21journeys drawn

By workflow

WorkflowJourneysStoriesScenariosPassing
Phase 1
W01 Patient Registration A patient is registered
A patient's record is maintained		 31 169 7
W02 Scheduling An appointment is booked and the patient checks in
The patient leaves with a visit summary
The scheduler keeps the schedule current		 14 104 15
W03 Pre-Visit / Triage (MA and nurse) A clinician signs on and finds a patient
A patient is roomed		 13 26 4
W04 Provider/MA Visit, Encounter and Note-Taking A provider sees the patient 17 43 1
W05 Diagnosis and Procedure Coding A visit is coded and billed 7 9 0
W06 After-Visit Summary and Care Plan The patient leaves with a visit summary 4 4 0
W07 Reporting (limited) A site manager runs the clinic's reports 2 2 0
W08 Billing and Revenue Cycle (Medicare and Medicaid) A visit is coded and billed 3 4 3
W09 Credentialing (limited) A provider is credentialed 3 3 0
Phase 2
W10 Prescriptions (Rx) A prescription is filled 2 2 0
W11 Lab Orders and Results A lab test is ordered and resulted 3 3 0
W12 Referrals and Consults A consult is sent and completed 3 5 0
W13 PRC (Purchased/Referred Care) Purchased/Referred Care is authorized 2 3 0
W14 Patient Messaging and Communication A patient message is answered 2 2 0
W15 Reporting (GPRA+) The GPRA report is run 3 4 0
W16 Credentialing (continued) A provider is credentialed 1 1 0
W17 Billing and Revenue Cycle (more programs, third party, clearinghouse) A visit is coded and billed 1 1 0
W18 Admission, Discharge and Transfer (ADT) A patient is admitted and discharged 6 23 0
W19 Benefits and Eligibility A patient's coverage is recorded 10 36 0
W20 Population and Care Management (iCare) A population is managed 8 15 0
W21 Behavioral Health Data Segregation (42 CFR Part 2) A behavioral health note is protected 4 12 0

The product cycle

The rollout's workflows, turned into artifacts that point at each other, so a workflow can be followed from the people who do it to the screen they do it on. The stories are drafts written from the chart's structure; the analyst's walkthroughs with the people who do the work are what correct them. Each scenario is accepted when a result for it, from the analyst or an automated test, is recorded against it.

Workflow -> Persona -> User story -> Journey (BPMN) step -> Screen -> Screenshot
                          |
                          +-> Concepts -> Data model (FileMan files) -> Backlog -> working software
PersonasWho does the workflows, and the RPMS user profile each is set up with.
Use casesEvery user story, by workflow, with its scenarios and the journey step it happens on.
Data modelThe RPMS files the workflows read and write.
JourneysThe workflows as BPMN, with each step's screenshot overlaid and its coverage coloured.

Reference

RPCsEvery RPC a build registers, with its arguments and reply: 5557 in 49 packages on bcer-9.0-20261012-e7923a4-ydb.
APIThe rpms-rpc gem's public methods as resources and verbs: 199 operations, 58 proven by a live spec.

Plan

Repositories