Coverage

How complete each flow is, on this branch's build (bcer-9.0-20260928-7e57c74-ydb). A flow is done when all three numbers are 100%: every step a person performs has a story, every scenario has an automated test, and every scenario is accepted. Accepted means both gates passed on this build: the analyst, and an automated test, each signed on as the scenario's persona (docs/product-cycle/DEFINITION_OF_DONE.md).

Passed by a test counts the scenarios an automated test has passed, from the results its runs recorded (results.tsv, written by cloud-rpms make record-results and bin/import-release-evidence.mjs), on any recent build; partial = the passing test asserts only part of the Then. Each result names its build and its evidence in the Automated column.

The test column is the dry run: the tests that exist or are planned for each scenario, before anything runs. written = a test asserts the scenario's Then; partial = a test exercises it but does not assert all of its Then; planned = written down, waiting on the driver that can run it; owed = a stub in the suite (cloud-rpms spec/scenarios/), no test yet; none = not in the suite at all.

Flow	Steps with a story	Scenarios with a test	Passed by a test	Accepted, Demo clinic
W01 Patient Registration	100% 11/11	5% 8/169, 58 partial, 1 planned, 102 owed	3% 5/169, 2 partial	0% 0/169
W02 Scheduling	100% 15/15	11% 11/104, 59 partial, 1 planned, 33 owed	11% 11/104, 4 partial	0% 0/104
W03 Pre-Visit / Triage (MA and nurse)	100% 14/14	0% 0/26, 8 partial, 17 planned, 1 owed	0% 0/26, 4 partial	0% 0/26
W04 Provider/MA Visit, Encounter and Note-Taking	100% 6/6	0% 0/43, 3 partial, 12 planned, 28 owed	0% 0/43, 1 partial	0% 0/43
W05 Diagnosis and Procedure Coding	100% 4/4	0% 0/9, 1 planned, 8 owed	0% 0/9	0% 0/9
W06 After-Visit Summary and Care Plan	100% 5/5	0% 0/4, 2 planned, 2 owed	0% 0/4	0% 0/4
W07 Reporting (limited)	100% 2/2	0% 0/2, 2 owed	0% 0/2	0% 0/2
W08 Billing and Revenue Cycle (Medicare and Medicaid)	100% 4/4	25% 1/4, 2 partial, 1 owed	25% 1/4, 2 partial	0% 0/4
W09 Credentialing (limited)	100% 3/3	0% 0/3, 3 owed	0% 0/3	0% 0/3
W10 Prescriptions (Rx) phase 2	100% 2/2	0% 0/2, 2 owed	0% 0/2	0% 0/2
W11 Lab Orders and Results phase 2	100% 3/3	0% 0/3, 3 owed	0% 0/3	0% 0/3
W12 Referrals and Consults phase 2	100% 3/3	0% 0/5, 1 planned, 4 owed	0% 0/5	0% 0/5
W13 PRC (Purchased/Referred Care) phase 2	100% 2/2	0% 0/3, 3 owed	0% 0/3	0% 0/3
W14 Patient Messaging and Communication phase 2	100% 2/2	0% 0/2, 2 owed	0% 0/2	0% 0/2
W15 Reporting (GPRA+) phase 2	100% 2/2	0% 0/4, 4 owed	0% 0/4	0% 0/4
W16 Credentialing (continued) phase 2	100% 3/3	0% 0/1, 1 owed	0% 0/1	0% 0/1
W17 Billing and Revenue Cycle (more programs, third party, clearinghouse) phase 2	100% 4/4	0% 0/1, 1 owed	0% 0/1	0% 0/1
W18 Admission, Discharge and Transfer (ADT) phase 2	100% 4/4	0% 0/23, 1 planned, 22 owed	0% 0/23	0% 0/23
W19 Benefits and Eligibility phase 2	100% 6/6	0% 0/36, 36 owed	0% 0/36	0% 0/36
W20 Population and Care Management (iCare) phase 2	100% 7/7	0% 0/15, 15 owed	0% 0/15	0% 0/15
W21 Behavioral Health Data Segregation (42 CFR Part 2) phase 2	100% 4/4	0% 0/12, 12 owed	0% 0/12	0% 0/12

W01 Patient Registration

Journeys: patient-is-registered.bpmn, patient-record-is-maintained.bpmn.

169 scenarios

Scenario	Test	Analyst	Automated
S-REG-01.1 `front_desk_clerk` Given a patient already registered at the facility, When I search by last name and date of birth, Then the patient is listed with their health record number and I can open their registration.	written cloud-rpms spec/features/cia_broker_rpc_spec.rb:222 (rpc, full, written; as staging pair) cloud-rpms spec/features/bprm_patient_search_spec.rb:39 (bprm, partial, written; as PROFILE,REG) cloud-rpms spec/features/bprm_patient_search_spec.rb:53 (bprm, partial, written; as PROFILE,REG) cloud-rpms spec/features/front_desk_clerk_spec.rb:43 (rpc, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_find_patient_test.rb:60 (lakeraven-ehr, partial, written; as PROFILE,REG) rpms-ops test/persona_walk.rb (rpc, partial, written; as PROFILE,REG)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REGSUP, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG
S-REG-01.2 `front_desk_clerk` Given no patient matches, When I search, Then I am offered to add a new patient.	written cloud-rpms spec/features/bprm_patient_search_spec.rb:60 (bprm, full, written; as PROFILE,REG) cloud-rpms spec/features/cia_broker_rpc_spec.rb:184 (rpc, partial, written; as staging pair) lakeraven-ehr test/integration/registration_find_patient_test.rb:86 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_register_patient_test.rb:247 (lakeraven-ehr, partial, written; as PROFILE,REG)	not run	not run
S-REG-01.3 `front_desk_clerk` Given a patient whose chart at this facility is inactive or deleted, When I search, Then the patient is listed with that chart status, so I do not mistake them for an active patient.	partial lakeraven-ehr test/integration/registration_find_patient_test.rb:75 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:7 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-01.4 `front_desk_clerk` Given a deceased patient, When I search, Then the patient is listed as deceased.	partial lakeraven-ehr test/integration/registration_find_patient_test.rb:75 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:13 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-01.5 `front_desk_clerk` Given a patient registered at another facility and not at this one, When I open their registration, Then I am asked for a health record number at this facility before anything else, and until one is filed in the HEALTH RECORD NO. multiple (#9000001.41) of IHS PATIENT (#9000001) the record cannot be edited here.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:19 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-01.6 `front_desk_clerk` Given I have the patient open at the front desk, When I send them to the EHR, Then the patient context for my user is set to this patient, so the EHR on my workstation opens on them.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:25 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-01.7 `front_desk_clerk` Given a patient identifier that is not in PATIENT (#2), When I open it, Then I am told there is no such patient and no record opens.	planned cloud-rpms spec/features/bprm_patient_search_spec.rb:70 (bprm, full, pending; as PROFILE,REG)	not run	not run
S-REG-02.1 `front_desk_clerk` Given no existing chart, When I enter name, sex, date of birth, tribe of membership and community of residence and save, Then the patient exists in PATIENT (#2) and IHS PATIENT (#9000001) with a health record number for this facility.	written cloud-rpms spec/features/bprm_registration_spec.rb:44 (bprm, full, written; as PROFILE,REG) rpms-ops bin/ydb_registration_evidence.sh (rpc, full, written; as PROFILE,REG) cloud-rpms spec/features/cia_broker_rpc_spec.rb:184 (rpc, partial, written; as staging pair) cloud-rpms spec/features/cia_broker_rpc_spec.rb:206 (rpc, partial, written; as staging pair) lakeraven-ehr test/integration/live_registration_register_patient_test.rb:39 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_register_patient_test.rb:74 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_register_patient_test.rb:263 (lakeraven-ehr, partial, written; as PROFILE,REG)	not run	pass 2026-10-02 on bcer-9.0-20260930-6812fea-iris, bprm as PROVIDER,TEST, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG
S-REG-02.2 `front_desk_clerk` Given a required field is missing, When I save, Then the registration is refused and names the field.	partial lakeraven-ehr test/integration/registration_register_patient_test.rb:87 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/models/lakeraven/ehr/patient_registration_test.rb:20 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:33 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.3 `front_desk_clerk` Given a patient already on file with the same name, date of birth and sex, When I enter the new patient's name, date of birth and sex, Then I am shown the possible matches, with their chart numbers, before anything is filed, and I can open one of them instead of registering.	written cloud-rpms spec/features/cia_broker_rpc_spec.rb:222 (rpc, full, written; as staging pair) lakeraven-ehr test/integration/live_registration_register_patient_test.rb:52 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_register_patient_test.rb:98 (lakeraven-ehr, partial, written; as PROFILE,REG)	not run	not run
S-REG-02.4 `front_desk_clerk` Given a name that is not `LAST,FIRST MIDDLE`, or shorter than 3 or longer than 30 characters, When I save, Then the registration is refused and names the format.	partial lakeraven-ehr test/models/lakeraven/ehr/patient_registration_test.rb:27 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:39 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.5 `front_desk_clerk` Given a date of birth in the future, or before 1871, When I save, Then the registration is refused.	partial lakeraven-ehr test/models/lakeraven/ehr/patient_registration_test.rb:40 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:45 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.6 `front_desk_clerk` Given no social security number and no reason for having none, When I save, Then the registration is refused and asks for the reason.	partial lakeraven-ehr test/integration/live_registration_register_patient_test.rb:96 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_register_patient_test.rb:303 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/models/lakeraven/ehr/patient_registration_test.rb:64 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:51 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.7 `front_desk_clerk` Given a social security number that is not nine digits, When I save, Then the registration is refused and names the format.	partial lakeraven-ehr test/models/lakeraven/ehr/patient_registration_test.rb:46 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:57 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.8 `front_desk_clerk` Given a social security number already on another patient in PATIENT (#2), When I save, Then the registration is refused and nothing is filed.	partial lakeraven-ehr test/integration/live_registration_register_patient_test.rb:80 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_register_patient_test.rb:316 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:63 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.9 `front_desk_clerk` Given a health record number already assigned to another patient at this facility, in any of its leading-zero or temporary forms, When I save, Then the registration is refused and names the number.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:69 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.10 `front_desk_clerk` Given a health record number that is not 1 to 6 characters in the chart-number format, When I save, Then the registration is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:75 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.11 `front_desk_clerk` Given I have not said whether the patient received the notice of privacy practices, or whether they are a veteran, When I save, Then the registration is refused and names what is missing.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:81 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.12 `front_desk_clerk` Given this facility's REGISTRATION PARAMETERS (#9009061) make the street address, city, state or zip code mandatory, When I save without one of them, Then the registration is refused and names the field.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:87 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.13 `front_desk_clerk` Given no primary language, or no community of residence and date moved there, When I save, Then the registration is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:93 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.14 `front_desk_clerk` Given a complete registration, When I save, Then IHS PATIENT (#9000001) holds today as the date established and me as the establishing user and the user of the last update, and the patient's registration event is raised for the packages that listen for it.	partial cloud-rpms spec/features/bprm_registration_spec.rb:44 (bprm, partial, written; as PROFILE,REG)	not run	not run
S-REG-02.15 `front_desk_clerk` Given I hold none of the keys that allow registering a patient (AGZMGR, AGZMENU, XUPROG, XUPROGMODE), When I open registration, Then I cannot add a patient.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:99 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-02.16 `front_desk_clerk` Given RPMS cannot be reached, When I save a registration, Then I am told the registration service is unavailable, nothing is filed, and my entries are kept so I can try again.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:105 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-03.1 `front_desk_clerk` Given a registered patient with Medicaid, When I add the Medicaid number and eligibility dates, Then the eligibility shows on the patient and is in force on today's date.	partial lakeraven-ehr test/integration/live_registration_coverage_test.rb:45 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_coverage_test.rb:58 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_coverage_test.rb:73 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_coverage_test.rb:88 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_coverage_test.rb:99 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:113 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-03.2 `front_desk_clerk` Given eligibility that has lapsed, When I check the patient in, Then I am warned before the visit is created.	partial lakeraven-ehr test/integration/live_registration_coverage_test.rb:69 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/scheduling_checkin_coverage_test.rb:47 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/scheduling_checkin_coverage_test.rb:57 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:119 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-03.3 `front_desk_clerk` Given an uninsured patient who has applied for Medicaid, When I record the application with its type and the date it was submitted, Then PATIENT APPLICATIONS (#9000045) holds the application for the patient with that type and date, and its overall status is PENDING.	partial lakeraven-ehr test/integration/live_registration_applications_test.rb:48 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_applications_test.rb:49 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_applications_test.rb:61 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_applications_test.rb:74 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_applications_test.rb:86 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_applications_test.rb:96 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_applications_test.rb:137 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:125 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-03.4 `front_desk_clerk` Given a recorded application, When I record that it was approved or denied, and on what date, Then the application's overall status is APPROVED or DENIED, and its submission holds that status on that date.	partial lakeraven-ehr test/integration/registration_applications_test.rb:106 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_applications_test.rb:117 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:131 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-03.5 `front_desk_clerk` Given an application recorded by mistake, When I mark it entered in error, Then its overall status is ENTERED IN ERROR and the application stays on file: AG does not delete application data.	partial lakeraven-ehr test/integration/live_registration_applications_test.rb:48 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_applications_test.rb:127 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:137 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-04.1 `front_desk_clerk` Given a patient whose record is marked sensitive, When I open them and accept that I have a need to know, Then the record opens and DG SECURITY LOG (#38.1) holds my access to the patient with the date, my user and the registration option.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:145 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-04.2 `front_desk_clerk` Given a patient whose record is marked sensitive, When I decline the warning, Then the record does not open and nothing is logged.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:151 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-04.3 `front_desk_clerk` Given a patient whose record is my own, When I try to open it, Then I am refused and the record does not open.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:157 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-04.4 `front_desk_clerk` Given a patient I am restricted from, or my own user has no social security number on file, When I try to open them, Then I am refused and told why, and the record does not open.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:163 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-04.5 `front_desk_clerk` Given a patient whose record is marked for a warning only, When I open them, Then I am warned and the record opens without a log entry.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:169 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-05.1 `scheduler` Given a caller with no chart, When I enter name, date of birth, sex and social security number and ask for a chart number to be generated, Then the patient exists in PATIENT (#2) and IHS PATIENT (#9000001) with me as the user who entered them, and the HEALTH RECORD NO. multiple (#9000001.41) holds a temporary number for this facility.	partial lakeraven-ehr test/integration/live_scheduling_quick_registration_test.rb:44 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_quick_registration_test.rb:77 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:177 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-REG-05.2 `scheduler` Given a caller with no chart and a chart number I have been given, When I enter it instead of asking for one, Then the HEALTH RECORD NO. multiple (#9000001.41) holds that number for this facility.	partial lakeraven-ehr test/integration/scheduling_quick_registration_test.rb:92 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:183 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-REG-05.3 `scheduler` Given a patient already on file with the same name, date of birth and sex, When I enter the caller's details, Then I am shown the possible matches and can pick one to book instead of registering again.	partial lakeraven-ehr test/integration/live_scheduling_quick_registration_test.rb:74 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_quick_registration_test.rb:103 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:189 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-REG-05.4 `scheduler` Given no social security number and no reason for having none, or a number already on another patient, When I save, Then it is refused and nothing is filed.	partial lakeraven-ehr test/integration/scheduling_quick_registration_test.rb:115 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:195 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-REG-05.5 `scheduler` Given a chart number already assigned to another patient at this facility, When I save, Then it is refused and names the number.	partial lakeraven-ehr test/integration/scheduling_quick_registration_test.rb:115 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:201 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-REG-05.6 `scheduler` Given I do not hold the scheduling registration key (SDZREGMENU), When I search and find no match, Then I am not offered to register the caller.	partial lakeraven-ehr test/integration/scheduling_quick_registration_test.rb:56 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_quick_registration_test.rb:68 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/models/lakeraven/ehr/capabilities_test.rb:32 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:207 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-REG-06.1 `front_desk_clerk` Given a patient with a chart at another facility and none at this one, When I add a health record number for this facility, Then the HEALTH RECORD NO. multiple (#9000001.41) of IHS PATIENT (#9000001) holds the number under this facility, and the other facility's number is unchanged.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:215 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-06.2 `front_desk_clerk` Given a patient who already has a chart at this facility, When I try to add another, Then I am told they are already registered here and nothing is filed.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:221 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-06.3 `front_desk_clerk` Given a number already assigned to another patient at this facility, in any of its leading-zero or temporary forms, When I save, Then it is refused and names the number.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:227 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-06.4 `front_desk_clerk` Given I hold the view-only key (AGZVIEWONLY) or not the registration key (AGZMENU), When I open a patient from another facility, Then I cannot add a chart number here.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:233 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-07.1 `front_desk_clerk` Given a tribal member, When I record eligibility status, classification, tribe of membership, Indian blood quantum, tribe quantum and enrollment number, Then IHS PATIENT (#9000001) holds those values.	partial cloud-rpms spec/features/bprm_registration_spec.rb:44 (bprm, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/live_registration_eligibility_test.rb:35 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_eligibility_test.rb:49 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_eligibility_test.rb:61 (lakeraven-ehr, partial, written; as PROFILE,REG)	not run	not run
S-REG-07.2 `front_desk_clerk` Given a patient with a second tribe, When I add it with its quantum, Then the OTHER TRIBE multiple (#9000001.43) of IHS PATIENT holds that tribe and quantum.	partial lakeraven-ehr test/integration/live_registration_tribes_test.rb:39 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_tribes_test.rb:19 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_tribes_test.rb:29 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_tribes_test.rb:39 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:241 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-07.3 `front_desk_clerk` Given an eligibility status that needs reasons, When I add each reason, Then the patient's ELIGIBILITY MODIFIERS multiple (#9000001.03401) holds one entry per reason, each pointing at ELIGIBILITY MODIFIERS (#9000030), and no reason twice.	partial lakeraven-ehr test/integration/live_registration_tribes_test.rb:52 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_tribes_test.rb:19 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_tribes_test.rb:63 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_tribes_test.rb:80 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:247 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-07.4 `front_desk_clerk` Given a classification of Indian or Alaska Native, When I save with an eligibility status of ineligible, or a tribe of NON-INDIAN, Then it is refused and says which value contradicts the other.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:253 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-07.5 `front_desk_clerk` Given an eligibility status of ineligible, or a classification of non-Indian or other, When I save with a tribe other than NON-INDIAN, Then it is refused and asks for NON-INDIAN.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:259 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-07.6 `front_desk_clerk` Given a blood quantum that is not a fraction or one of FULL, NONE, UNKNOWN or UNSPECIFIED, or a fraction over 1, When I save, Then it is refused and names the form.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:265 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-07.7 `front_desk_clerk` Given a tribe of NON-INDIAN, When I save a blood quantum other than NONE or UNKNOWN, Then it is refused; and given any other tribe, a quantum of NONE or UNKNOWN is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:271 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-07.8 `front_desk_clerk` Given a tribe quantum, or another tribe's quantum, greater than the Indian blood quantum, When I save, Then it is refused.	partial lakeraven-ehr test/integration/registration_tribes_test.rb:52 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:277 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-07.9 `front_desk_clerk` Given another tribe that is the tribe of membership, or listed twice, When I save, Then it is refused.	partial lakeraven-ehr test/integration/registration_tribes_test.rb:52 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:283 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-08.1 `front_desk_clerk` Given a patient, When I record an emergency contact's name, relationship, address and phones, Then PATIENT (#2) holds the emergency contact's name, address and phones and IHS PATIENT (#9000001) holds the relationship; the same holds for the next of kin.	partial lakeraven-ehr test/integration/live_registration_contacts_test.rb:41 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_contacts_test.rb:14 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_contacts_test.rb:26 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:291 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-08.2 `front_desk_clerk` Given an emergency contact on file with an address and phones, When I change the contact's name and save nothing else, Then the previous contact's address and phones are cleared, not carried over to the new person.	partial lakeraven-ehr test/integration/live_registration_contacts_test.rb:41 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_contacts_test.rb:42 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:297 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-08.3 `front_desk_clerk` Given a contact name that is not `LAST,FIRST MIDDLE,SUFFIX`, or shorter than 3 characters, When I save, Then it is refused and names the format.	partial lakeraven-ehr test/integration/live_registration_contacts_test.rb:60 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_contacts_test.rb:52 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_contacts_test.rb:63 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:303 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-08.4 `front_desk_clerk` Given a relationship, address or phone for a contact but no name, When I save, Then it is refused and asks for the name.	partial lakeraven-ehr test/integration/registration_contacts_test.rb:73 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:309 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-09.1 `front_desk_clerk` Given a minor patient, When I record the father's name, the mother's maiden name, their relationship, phones, employer, email and place of birth, Then PATIENT (#2) holds the two names and IHS PATIENT (#9000001) holds the rest.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:317 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-09.2 `front_desk_clerk` Given a patient with a guardian who is not a parent, When I record the guardian's name and relationship, and a second guardian if there is one, Then IHS PATIENT (#9000001) holds each guardian with their relationship and contact details.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:323 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-09.3 `front_desk_clerk` Given a guardian's relationship but no name, or a name but no relationship, When I save, Then it is refused and names what is missing.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:329 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-09.4 `front_desk_clerk` Given a parent or guardian name that is not `LAST,FIRST MIDDLE,SUFFIX`, When I save, Then it is refused and names the format.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:335 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-09.5 `front_desk_clerk` Given a household size of 100 or more, or an income of 0 or of 10,000,000 or more, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:341 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-09.6 `front_desk_clerk` Given this facility requires the household income, When I save without the income or its period, Then it is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:347 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-10.1 `front_desk_clerk` Given a patient, When I record their primary language, preferred language, English proficiency and other languages, Then the LANGUAGES ENTRY DATE multiple (#9000001.86) of IHS PATIENT holds a new entry dated today with those values and one line per other language, and earlier entries are kept.	partial lakeraven-ehr test/integration/live_registration_languages_test.rb:37 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_languages_test.rb:18 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_languages_test.rb:82 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:355 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-10.2 `front_desk_clerk` Given a primary or other language of English, When I save without an English proficiency, or with a proficiency of not at all, Then it is refused.	partial lakeraven-ehr test/integration/registration_languages_test.rb:30 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:361 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-10.3 `front_desk_clerk` Given a primary language other than English, When I save without saying whether an interpreter is needed, Then it is refused and asks for it.	partial lakeraven-ehr test/integration/registration_languages_test.rb:44 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:367 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-10.4 `front_desk_clerk` Given an other language that is the primary language, or listed twice, When I save, Then it is refused.	partial lakeraven-ehr test/integration/registration_languages_test.rb:55 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:373 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-10.5 `front_desk_clerk` Given a preferred language that is neither the primary language nor one of the other languages, When I save, Then I am warned and may still save.	partial lakeraven-ehr test/integration/registration_languages_test.rb:67 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:379 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-11.1 `front_desk_clerk` Given a patient who is homeless, When I record that with the type, Then the HOMELESS STATUS QUESTION DATE multiple (#9000001.85) of IHS PATIENT holds a new entry dated today with the status and type, and earlier answers are kept.	partial lakeraven-ehr test/integration/live_registration_social_status_test.rb:40 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_social_status_test.rb:16 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:387 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-11.2 `front_desk_clerk` Given a patient who is a migrant worker, When I record that with the type, Then the MIGRANT WORKER QUESTION DATE multiple (#9000001.84) of IHS PATIENT holds a new entry dated today with the status and type.	partial lakeraven-ehr test/integration/live_registration_social_status_test.rb:40 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_social_status_test.rb:16 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:393 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-11.3 `front_desk_clerk` Given a status of homeless or migrant worker, When I save without the type, Then it is refused and asks for the type.	partial lakeraven-ehr test/integration/registration_social_status_test.rb:28 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:399 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-11.4 `front_desk_clerk` Given a status of not homeless, When I save with a type, Then the entry is filed without a type.	partial lakeraven-ehr test/integration/live_registration_social_status_test.rb:58 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_social_status_test.rb:40 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:405 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-12.1 `front_desk_clerk` Given a patient, When I record a preferred name, Then IHS PATIENT (#9000001) holds it and the patient is listed with it beside their legal name.	partial lakeraven-ehr test/integration/live_registration_preferred_name_test.rb:39 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:11 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:22 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:32 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:42 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:52 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:63 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:73 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:83 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_preferred_name_test.rb:92 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:413 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-12.2 `front_desk_clerk` Given a patient who has used other names, When I add each one, Then the OTHER NAME multiple (#2.01) of PATIENT (#2) holds each of them and a search by one of them lists the patient.	partial lakeraven-ehr test/integration/live_registration_other_names_test.rb:35 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_other_names_test.rb:13 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_other_names_test.rb:23 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:419 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-12.3 `front_desk_clerk` Given an other name that is not `LAST,FIRST MIDDLE`, or shorter than 3 or longer than 30 characters, When I save, Then it is refused and names the format.	partial lakeraven-ehr test/integration/registration_other_names_test.rb:33 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:425 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-12.4 `front_desk_clerk` Given an other name entered in error, When I remove it, Then the OTHER NAME multiple (#2.01) no longer holds it and the others are unchanged.	partial lakeraven-ehr test/integration/live_registration_other_names_test.rb:35 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_other_names_test.rb:46 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:431 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-13.1 `front_desk_clerk` Given a patient, When I record a legal sex with its effective date and the document that is the source, Then the LEGAL SEX multiple (#9000001.9201) of IHS PATIENT holds that entry with the date it was entered, and an earlier entry with another effective date is kept.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:439 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-13.2 `front_desk_clerk` Given two legal sex entries with the same effective date, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:445 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-13.3 `front_desk_clerk` Given a patient, When I record one or more gender identities and sexual orientations, Then the GENDER IDENTITY (#9000001.9401) and SEXUAL ORIENTATION (#9000001.9301) multiples of IHS PATIENT each hold today's entry with every choice, and an entry from an earlier date is kept.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:451 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-13.4 `front_desk_clerk` Given a gender identity, sexual orientation or pronoun of other, When I save without saying what, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:457 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-13.5 `front_desk_clerk` Given a patient, When I record their pronouns, Then IHS PATIENT (#9000001) holds the pronouns and, for other, the text.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:463 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-14.1 `front_desk_clerk` Given a veteran, When I record the branch, entry and separation dates, service-connected status, Vietnam service and claim number, Then PATIENT (#2) holds those values and IHS PATIENT (#9000001) holds today as the date the veteran information was edited.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:471 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-14.2 `front_desk_clerk` Given a veteran with a valid VA card, When I record the date a copy was obtained, Then IHS PATIENT (#9000001) holds the card as valid with that date; and given no valid card, it holds whether they were told how to obtain one and no copy date.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:477 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-14.3 `front_desk_clerk` Given a service entry date after the separation date, or either date in the future or before 1871, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:483 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-14.4 `front_desk_clerk` Given a claim number that is not 7 or 8 digits, When I save, Then it is refused and names the format.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:489 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-15.1 `front_desk_clerk` Given a patient, When I record that they received the notice of privacy practices on a date and signed the acknowledgement, Then NOTICE OF PRIVACY PRACTICES (#9000038) holds the patient with those answers, me and today's date.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:497 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-15.2 `front_desk_clerk` Given a patient who received the notice but did not sign, When I save without a reason, Then it is refused and asks for the reason; and given they did not receive it, no acknowledgement or reason is kept.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:503 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-15.3 `front_desk_clerk` Given a patient, When I record the date benefits were assigned, Then the ASSIGN BENEFITS OBTAINED DATE multiple (#9000001.71) of IHS PATIENT (#9000001) holds a new entry for that date, and a second entry for the same date is not added.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:509 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-15.4 `front_desk_clerk` Given a patient, When I record the date they signed the release of information, Then the RELEASE OF INFORMATION multiple (#9000001.03601) of IHS PATIENT (#9000001) holds an entry for that date.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:515 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-15.5 `front_desk_clerk` Given an assignment or release date in the future, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:521 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-15.6 `front_desk_clerk` Given this facility's REGISTRATION PARAMETERS (#9009061) make the release of information or the assignment of benefits mandatory, When I save without one, Then it is refused and names it.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:527 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-15.7 `front_desk_clerk` Given a patient, When I record whether they were granted access to their personal health record on a date, and the date they were given the handout, Then the PHR ACCESS DATE (#9000001.8801) and PHR HANDOUT DATE (#9000001.8901) multiples of IHS PATIENT hold those entries, and a second entry for the same date is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:533 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-16.1 `front_desk_clerk` Given an adult patient, When I record their consent or refusal with the effective date and an expiration date, Then the sharing consent multiple of IHS PATIENT (#9000001) holds a new entry with those dates and this facility, and earlier entries are kept unchanged.	partial cloud-rpms spec/features/bprm_registration_spec.rb:69 (bprm, partial, written; as PROFILE,REG)	not run	pass 2026-10-02 on bcer-9.0-20260930-6812fea-iris, bprm as PROVIDER,TEST
S-REG-16.2 `front_desk_clerk` Given an effective date in the future, more than five years ago, or before the patient's date of birth, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:541 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-16.3 `front_desk_clerk` Given an expiration date on or before the effective date, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:547 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-16.4 `front_desk_clerk` Given a patient under 18, When I open their registration, Then no sharing consent can be recorded for them and none is counted as missing.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:553 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-17.1 `front_desk_clerk` Given a patient with a living will, When I record the directive with its type and date of entry, Then ADVANCE DIRECTIVE (#9000040) holds the patient and its DATE OF ENTRY multiple (#9000040.11) holds the directive with that type and date.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:561 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-17.2 `front_desk_clerk` Given a patient with no directive, When I record that with the reason, Then the DATE OF ENTRY multiple (#9000040.11) of ADVANCE DIRECTIVE holds the answer with the reason.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:567 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-17.3 `front_desk_clerk` Given a directive of the same type already on file for that date, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:573 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-17.4 `front_desk_clerk` Given a directive with no type, or no directive with no reason, or no date of entry, When I save, Then it is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:579 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-17.5 `front_desk_clerk` Given a directive entered in error, When I remove it, Then the DATE OF ENTRY multiple (#9000040.11) of ADVANCE DIRECTIVE no longer holds it.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:585 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-18.1 `front_desk_clerk` Given a patient, When I record a legal document with its type, document number, the date it was added to the file and its effective and end dates, Then PATIENT'S LEGAL DOCS (#9000034) holds it for the patient with me and today as the entry.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:593 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-18.2 `front_desk_clerk` Given no document type or no date added to file, When I save, Then it is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:599 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-18.3 `front_desk_clerk` Given an end date before the effective date, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:605 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-18.4 `front_desk_clerk` Given a document on file, When I correct its dates, or remove it, Then PATIENT'S LEGAL DOCS (#9000034) holds the corrected dates, or no longer holds it.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:611 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-19.1 `front_desk_clerk` Given a patient, When I write notes and save, Then the notes word-processing field of IHS PATIENT (#9000001) holds the text, however long.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:619 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-19.2 `front_desk_clerk` Given notes on file, When I clear them and save, Then IHS PATIENT (#9000001) holds no notes for the patient.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:625 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.1 `front_desk_clerk` Given a registered patient, When I change their date of birth, sex, marital status, religion, place of birth, employer or employment status, Then PATIENT (#2) and IHS PATIENT (#9000001) hold the new values.	partial lakeraven-ehr test/integration/live_registration_edit_patient_test.rb:68 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_edit_patient_test.rb:74 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_edit_patient_test.rb:89 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:633 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.2 `front_desk_clerk` Given a registered patient, When I record one or more races and ethnicities with how each was collected, Then the RACE INFORMATION multiple (#2.02) and the ethnicity multiple of PATIENT (#2) hold one entry per race and ethnicity, each pointing at RACE (#10) or ETHNICITY (#10.2), with its collection method.	partial lakeraven-ehr test/integration/live_registration_address_history_race_test.rb:70 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_race_ethnicity_test.rb:30 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_race_ethnicity_test.rb:41 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_race_ethnicity_test.rb:54 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_race_ethnicity_test.rb:91 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:639 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.3 `front_desk_clerk` Given no race or no ethnicity, When I save, Then it is refused and names which.	partial lakeraven-ehr test/integration/registration_race_ethnicity_test.rb:66 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:645 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.4 `front_desk_clerk` Given the same race or ethnicity listed twice, or unknown or declined together with another, When I save, Then it is refused.	partial lakeraven-ehr test/integration/registration_race_ethnicity_test.rb:78 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:651 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.5 `front_desk_clerk` Given an employer but no employment status, When I save, Then it is refused and asks for the status.	partial lakeraven-ehr test/integration/registration_edit_patient_test.rb:104 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:657 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.6 `front_desk_clerk` Given a registered patient, When I record their industries and occupations, Then the INDUSTRY-OCCUPATION multiple (#9000001.5201) of IHS PATIENT holds today's entry with one line per pair, no industry twice, and each with both an industry and an occupation.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:663 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.7 `front_desk_clerk` Given a social security number already on another patient, When I change the patient's number to it, Then it is refused and nothing is filed.	partial lakeraven-ehr test/integration/live_registration_edit_patient_test.rb:87 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_edit_patient_test.rb:115 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:669 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.8 `front_desk_clerk` Given I do not hold the key that shows social security numbers (AGZVIEWSSN), When I open the patient, Then the number is not shown to me.	partial lakeraven-ehr test/integration/registration_edit_patient_test.rb:128 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:675 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.9 `front_desk_clerk` Given I hold only the view-only key (AGZVIEWONLY), When I open a patient, Then I can see the registration and change nothing.	partial lakeraven-ehr test/integration/registration_edit_patient_test.rb:141 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:681 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-20.10 `front_desk_clerk` Given a patient whose name was misspelled at registration, When I correct the spelling without a change of legal name, Then PATIENT (#2) holds the corrected name and PATIENT NAME CHANGES (#9000033) is unchanged.	partial lakeraven-ehr test/integration/live_registration_edit_patient_test.rb:68 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_edit_patient_test.rb:158 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:687 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-21.1 `front_desk_clerk` Given a patient with an address on file, When I change the street address, city, state, zip code or home phone, with the date they moved, Then PATIENT (#2) holds the new address and the PREVIOUS MAIL ADDRESSES multiple (#9000001.83) of IHS PATIENT (#9000001) holds the old one, ended on the date they moved.	partial lakeraven-ehr test/integration/live_registration_address_history_race_test.rb:44 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/live_registration_edit_patient_test.rb:100 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_edit_patient_test.rb:168 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_edit_patient_test.rb:180 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_edit_patient_test.rb:194 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_edit_patient_test.rb:207 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_edit_patient_test.rb:228 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:695 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-21.2 `front_desk_clerk` Given a street address typed with abbreviations, or a post office box or rural route in any of its common forms, When I save, Then I am shown the postal standard form and PATIENT (#2) holds the address in that form.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:701 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-21.3 `front_desk_clerk` Given this facility's REGISTRATION PARAMETERS (#9009061) make the street address, city, state or zip code mandatory, When I save without one, Then it is refused and names the field.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:707 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-21.4 `front_desk_clerk` Given a zip code that is not 1 to 10 letters and digits, or a phone shorter than 4 digits, When I save, Then it is refused and names the format.	partial lakeraven-ehr test/integration/registration_edit_patient_test.rb:239 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_edit_patient_test.rb:250 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:713 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-21.5 `front_desk_clerk` Given a patient, When I change their cell phone, work phone, other phone, email, reminder preference or pharmacy residence, Then PATIENT (#2) holds the phones and IHS PATIENT (#9000001) holds the rest, and the PREVIOUS EMAIL ADDRESSES multiple (#9000001.82) holds the email that was replaced.	partial lakeraven-ehr test/integration/live_registration_edit_patient_test.rb:100 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_edit_patient_test.rb:261 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:719 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-21.6 `front_desk_clerk` Given an email address that is not in email form, When I save, Then it is refused.	partial lakeraven-ehr test/integration/registration_edit_patient_test.rb:261 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:725 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-21.7 `front_desk_clerk` Given a date lived from that is in the future, before 1871 or before the patient's date of birth, When I save, Then it is refused.	partial lakeraven-ehr test/integration/registration_edit_patient_test.rb:216 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:731 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-22.1 `front_desk_clerk` Given a patient who has moved to another community, When I record the community and the date moved, Then the PREVIOUS COMMUNITY multiple (#9000001.51) of IHS PATIENT (#9000001) holds the community under that date, and IHS PATIENT (#9000001) holds it as the current community when the date is on or after the current one.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:739 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-22.2 `front_desk_clerk` Given a community that was inactive on the date moved, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:745 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-22.3 `front_desk_clerk` Given a date moved in the future, before 1871, or before the patient's date of birth, or no community or date, When I save, Then it is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:751 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-22.4 `front_desk_clerk` Given a patient whose home is hard to find, When I write directions and save, Then the location-of-home word-processing field of IHS PATIENT (#9000001) holds them; and when I clear them, it holds none.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:757 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-22.5 `front_desk_clerk` Given a patient, When I record that they can use the internet and from where, Then the INTERNET ACCESS QUESTION DATE multiple (#9000001.81) of IHS PATIENT holds today's answer with each place, and earlier answers are kept.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:763 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-22.6 `front_desk_clerk` Given an answer that they can use the internet, When I save without saying from where, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:769 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-22.7 `front_desk_clerk` Given a previous address on file, When I correct its lines or the dates it was lived at, Then the PREVIOUS MAIL ADDRESSES multiple (#9000001.83) holds the corrected entry.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:775 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-22.8 `front_desk_clerk` Given a date lived to before the date lived from, or either date in the future or before 1871, When I save a previous address, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:781 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-23.1 `front_desk_clerk` Given a patient with no privacy notice on file, an address older than the facility allows, or coverage that has lapsed, When I open their registration, Then each error and warning is listed against the section it belongs to, with errors counted apart from warnings.	partial lakeraven-ehr test/integration/live_registration_missing_items_test.rb:45 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_missing_items_test.rb:51 (lakeraven-ehr, partial, written; as PROFILE,REG) cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:789 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-23.2 `front_desk_clerk` Given an error listed for a missing item, When I record the item, Then the error is no longer listed.	written cloud-rpms spec/features/bprm_registration_spec.rb:69 (bprm, full, written; as PROFILE,REG) lakeraven-ehr test/integration/live_registration_missing_items_test.rb:45 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_missing_items_test.rb:66 (lakeraven-ehr, partial, written; as PROFILE,REG)	not run	pass 2026-10-02 on bcer-9.0-20260930-6812fea-iris, bprm as PROVIDER,TEST
S-REG-23.3 `front_desk_clerk` Given a patient under 18, When I open their registration, Then a missing sharing consent is not listed against them.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:795 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-24.1 `front_desk_clerk` Given a patient with a privacy notice, assignment of benefits, release of information, advance directive, legal document, sharing consent, personal health record access, name change and restricted health information on file, When I open their documents, Then each is listed with its date, drawn from NOTICE OF PRIVACY PRACTICES (#9000038), the ASSIGN BENEFITS OBTAINED DATE (#9000001.71) and RELEASE OF INFORMATION (#9000001.03601) multiples, ADVANCE DIRECTIVE (#9000040), PATIENT'S LEGAL DOCS (#9000034), PATIENT NAME CHANGES (#9000033) and RESTRICTED HEALTH INFORMATION (#9000039).	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:803 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-24.2 `front_desk_clerk` Given a patient, When I print their face sheet, index card or wrist band, Then the printout carries the registration as filed in PATIENT (#2) and IHS PATIENT (#9000001) on that day, and nothing is stored.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:809 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-REG-25.1 `registration_supervisor` Given a patient with a chart at this facility, When I change the number, Then the HEALTH RECORD NO. multiple (#9000001.41) of IHS PATIENT (#9000001) holds the new number under this facility.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:817 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-25.2 `registration_supervisor` Given a number already assigned to another patient at this facility, or not 1 to 6 characters in the chart-number format, When I save, Then it is refused and names the number.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:823 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-25.3 `registration_supervisor` Given a chart registered in error, sent to archives or inactive, When I set that disposition with the date, Then the HEALTH RECORD NO. multiple (#9000001.41) holds the disposition, a status of inactivated and that date, the patient is listed with that status, and their registration can no longer be edited at this facility.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:829 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-25.4 `registration_supervisor` Given an inactivated chart, When I set the disposition to reactivated or new chart, Then the HEALTH RECORD NO. multiple (#9000001.41) holds the disposition with no status and no inactivation date, and the registration can be edited again.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:835 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-25.5 `registration_supervisor` Given I do not hold the registration manager key (AGZMGR), When I open a patient, Then I cannot change their chart number or disposition.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:841 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-26.1 `registration_supervisor` Given a patient with proof of a new name, When I record the new name, the proof provided and the document number, Then PATIENT (#2) holds the new name, PATIENT NAME CHANGES (#9000033) holds the change with the date, proof and document, and the OTHER NAME multiple (#2.01) holds the former name.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:849 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-26.2 `registration_supervisor` Given no proof provided, or a name that is not `LAST,FIRST MIDDLE` or outside 3 to 30 characters, When I save, Then it is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:855 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-26.3 `registration_supervisor` Given a name change on file, When I correct its proof or document number, Then PATIENT NAME CHANGES (#9000033) holds the correction and the patient's name is unchanged.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:861 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-26.4 `registration_supervisor` Given I do not hold the registration manager key (AGZMGR), When I open a patient, Then I cannot change their legal name.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:867 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-27.1 `registration_supervisor` Given a living patient, When I record the date and time of death, the state, the certificate number and the preliminary cause, Then PATIENT (#2) holds the date of death and me as the user who entered it, IHS PATIENT (#9000001) holds the state, certificate number and the date edited, and the patient is listed as deceased.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:875 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-27.2 `registration_supervisor` Given a date of death before the patient's date of birth, or in the future, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:881 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-27.3 `registration_supervisor` Given a death on file, When any user opens the patient, Then the registration can be seen and nothing in it changed.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:887 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-27.4 `registration_supervisor` Given a death entered in error, When I clear it, Then PATIENT (#2) holds no date of death and the registration can be edited again.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:893 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-27.5 `registration_supervisor` Given I do not hold the registration manager key (AGZMGR), When I open a patient, Then I cannot record or clear a death.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:899 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-28.1 `him_technician` Given a patient and a flag from PRF NATIONAL FLAG (#26.15) or PRF LOCAL FLAG (#26.11), When I assign it with the owner site, the narrative, who approved it and the review date, Then PRF ASSIGNMENT (#26.13) holds an active assignment for the patient with those values and the narrative, PRF ASSIGNMENT HISTORY (#26.14) holds a new-assignment action entered by me and approved by that person, and the patient is listed as flagged.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:907 (bprm, full, owed; as -)	not run	not run
S-REG-28.2 `him_technician` Given a flag already assigned to the patient, When I assign the same flag again, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:913 (bprm, full, owed; as -)	not run	not run
S-REG-28.3 `him_technician` Given a flag with a review frequency, When I save with a review date before today, after today plus the frequency, or none, Then it is refused and names the date.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:919 (bprm, full, owed; as -)	not run	not run
S-REG-28.4 `him_technician` Given no owner site, narrative, approver or flag, When I save, Then it is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:925 (bprm, full, owed; as -)	not run	not run
S-REG-28.5 `him_technician` Given an active assignment, When I continue or reactivate it with a reason, an approver and a new review date, Then PRF ASSIGNMENT (#26.13) holds the new review date and an active status, and PRF ASSIGNMENT HISTORY (#26.14) holds that action with the reason.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:931 (bprm, full, owed; as -)	not run	not run
S-REG-28.6 `him_technician` Given an active assignment, When I inactivate it, or mark it entered in error, with a reason and an approver, Then PRF ASSIGNMENT (#26.13) holds an inactive status and PRF ASSIGNMENT HISTORY (#26.14) holds that action with the reason, and the patient is no longer listed as flagged for it.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:937 (bprm, full, owed; as -)	not run	not run
S-REG-28.7 `him_technician` Given I do not hold the flag assignment key (DGPF ASSIGNMENT), When I open a patient, Then I cannot assign a new flag.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:943 (bprm, full, owed; as -)	not run	not run
S-REG-29.1 `him_technician` Given a patient who asks for a restriction, When I record it as pending with the date and the reason, Then RESTRICTED HEALTH INFORMATION (#9000039) holds the patient with that status, reason and date, entered by me today, and the patient is listed as restricted.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:951 (bprm, full, owed; as -)	not run	not run
S-REG-29.2 `him_technician` Given a pending request, When I record it as approved with the date and the approving official, Then RESTRICTED HEALTH INFORMATION (#9000039) holds the approval with that official and date, by me today.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:957 (bprm, full, owed; as -)	not run	not run
S-REG-29.3 `him_technician` Given a request, When I record it as not approved, or revoked, with the date and the official, Then RESTRICTED HEALTH INFORMATION (#9000039) holds that status with the official and date.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:963 (bprm, full, owed; as -)	not run	not run
S-REG-29.4 `him_technician` Given a status that needs a date or an official, When I save without them, or with an official's name outside 3 to 20 characters, or with no reason, Then it is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:969 (bprm, full, owed; as -)	not run	not run
S-REG-29.5 `him_technician` Given a request entered in error, When I mark it so, Then RESTRICTED HEALTH INFORMATION (#9000039) holds that status with me and today, and the patient is no longer listed as restricted.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:975 (bprm, full, owed; as -)	not run	not run
S-REG-30.1 `registration_supervisor` Given patients added and edited over a date range, When I run the daily activity report for those dates, Then it lists the patients by the date of their last registration update in IHS PATIENT (#9000001), or the counts of new, edited and removed, as I chose.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:983 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-30.2 `registration_supervisor` Given patients registered quickly with a generated chart number, When I run the temporary charts report, Then it lists each patient whose number in the HEALTH RECORD NO. multiple (#9000001.41) at this facility is temporary.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:989 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-30.3 `registration_supervisor` Given patients with coverage on file, When I run the insurance coverage or enrollment report for a resource, age range and eligibility status, Then it lists the patients whose coverage matches.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:995 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-30.4 `registration_supervisor` Given I hold none of the keys that allow the reports (AGZMGR, AGZMENU, AGZVIEWONLY), When I open registration, Then I cannot run them.	owed cloud-rpms spec/scenarios/phase1/w01_patient_registration_spec.rb:1001 (bprm, full, owed; as PROFILE,REGSUP)	not run	not run
S-REG-31.1 `front_desk_clerk` Given a patient just registered with the minimum, When I open their registration, Then each required item still missing is listed as an error, and each question not yet asked as a warning, against the section it belongs to.	written cloud-rpms spec/features/bprm_registration_spec.rb:69 (bprm, full, written; as PROFILE,REG) lakeraven-ehr test/integration/live_registration_missing_items_test.rb:45 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_missing_items_test.rb:51 (lakeraven-ehr, partial, written; as PROFILE,REG)	not run	pass 2026-10-02 on bcer-9.0-20260930-6812fea-iris, bprm as PROVIDER,TEST
S-REG-31.2 `front_desk_clerk` Given those errors, When I record each missing item, Then no error is listed against the patient's registration, and each item I recorded is on file in RPMS.	written cloud-rpms spec/features/bprm_registration_spec.rb:69 (bprm, full, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_missing_items_test.rb:76 (lakeraven-ehr, partial, written; as PROFILE,REG)	not run	pass 2026-10-02 on bcer-9.0-20260930-6812fea-iris, bprm as PROVIDER,TEST
S-REG-31.3 `front_desk_clerk` Given those warnings, When I answer each question, Then no warning is listed against the patient's registration, no section carries a mark, and each answer is on file in RPMS dated today.	written cloud-rpms spec/features/bprm_registration_spec.rb:69 (bprm, full, written; as PROFILE,REG) lakeraven-ehr test/integration/live_registration_social_status_test.rb:40 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/registration_missing_items_test.rb:76 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/registration_social_status_test.rb:49 (lakeraven-ehr, partial, written; as -)	not run	pass 2026-10-02 on bcer-9.0-20260930-6812fea-iris, bprm as PROVIDER,TEST

W02 Scheduling

Journeys: appointment-is-booked.bpmn, visit-summary-is-given.bpmn, schedule-is-maintained.bpmn.

104 scenarios

Scenario	Test	Analyst	Automated
S-SCH-01.1 `scheduler` Given a clinic with open slots on a date, When I pick a slot and a registered patient, Then the appointment shows on the clinic's schedule and in the patient's appointments.	written cloud-rpms spec/features/bprm_scheduling_spec.rb:42 (bprm, full, written; as PROFILE,SCHED) cloud-rpms spec/features/scheduler_day_spec.rb:244 (rpc, full, written; as PROFILE,SCHED) cloud-rpms spec/features/scheduler_spec.rb:46 (rpc, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:29 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:89 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/models/lakeraven/ehr/wall_clock_test.rb:31 (lakeraven-ehr, partial, written; as -) rpms-ops test/persona_walk.rb (rpc, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-01.2 `scheduler` Given a slot that is full, When I try to book it, Then I am told it is full, or asked to overbook if I hold the key for it.	partial lakeraven-ehr test/integration/live_scheduling_overbook_test.rb:29 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:99 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_overbook_test.rb:61 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:7 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.3 `scheduler` Given a slot chosen but no patient, date, time or appointment length, When I save, Then it is refused and names the missing value, and nothing is filed.	partial lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:121 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:13 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.4 `scheduler` Given a note on the appointment shorter than 2 or longer than 150 characters, or one containing a semicolon or a colon, When I save, Then it is refused and no appointment is filed.	partial lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:133 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:19 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.5 `scheduler` Given the patient already has an active appointment (not cancelled, not a no-show) at that date and time in PATIENT (#2.98), When I book, Then it is refused and the existing appointment is unchanged.	partial lakeraven-ehr test/gateways/lakeraven/ehr/appointment_booking_gateway_test.rb:45 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:29 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:144 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:25 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.6 `scheduler` Given a patient with a date of death in PATIENT (#2), When I book, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:31 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.7 `scheduler` Given a clinic whose inactivate date in HOSPITAL LOCATION (#44) is on or before the chosen date and whose reactivate date is absent or later, When I book, Then it is refused and nothing is filed.	partial lakeraven-ehr test/integration/scheduling_overbook_test.rb:126 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:190 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_walk_in_test.rb:98 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:37 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.8 `scheduler` Given a date further ahead than the clinic's maximum days for future booking in HOSPITAL LOCATION (#44), When I book, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:43 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.9 `scheduler` Given a time with no access block for the clinic's resource in BSDX ACCESS BLOCK (#9002018.3), or one whose access type in BSDX ACCESS TYPE (#9002018.35) prevents access, When I book without the master overbook right on that resource in BSDX RESOURCE USER (#9002018.15) and without SDZSUP, Then it is refused; with either, I am asked to confirm and the appointment is filed as an overbook.	partial lakeraven-ehr test/integration/scheduling_overbook_test.rb:109 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:49 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.10 `scheduler` Given a slot whose active appointments already equal the block's slot count, the overbook right on that resource for me in BSDX RESOURCE USER (#9002018.15), and fewer overbooks today on the clinic than its OVERBOOKS/DAY MAXIMUM (#44, field 1918), When I confirm the overbook, Then the appointment is on the clinic in HOSPITAL LOCATION (#44.003) and on the patient in PATIENT (#2.98), marked as an overbook in OVERBOOK (#44.003, field 9). (BPRM sets it itself after `MAKE^BSDAPI`, in `BSD_SetPatientAppointmentV4M`. Neither MAKE^BSDAPI nor BSDX ADD NEW APPOINTMENT sets it, so a booking through the BSDX RPC is not marked.)	partial lakeraven-ehr test/integration/live_scheduling_overbook_test.rb:29 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_overbook_test.rb:70 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_overbook_test.rb:138 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:55 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.11 `scheduler` Given a full slot and the clinic's overbooks for that day already at its maximum, and I hold neither the master overbook right on the resource nor SDZSUP, When I try to book, Then it is refused and no appointment is filed.	partial lakeraven-ehr test/integration/scheduling_overbook_test.rb:87 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_overbook_test.rb:98 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_overbook_test.rb:148 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:61 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.12 `scheduler` Given I hold neither SDZSUP nor SDZMENU, When I open scheduling, Then I cannot see a clinic's schedule or book, cancel, check in, check out or run a scheduling report.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:158 (lakeraven-ehr, partial, written; as PROFILE,REG) lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:70 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:67 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.13 `scheduler` Given a clinic whose resource gives my user no right to modify appointments in BSDX RESOURCE USER (#9002018.15), or a clinic marked as prohibiting access in HOSPITAL LOCATION (#44), and I do not hold SDZSUP, When I open its schedule, Then I can see it but cannot book, cancel, check in or out, or mark a no-show on it.	partial lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:155 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:201 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:214 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_book_appointment_test.rb:223 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:73 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-01.14 `scheduler` Given a clinic that is not in HOSPITAL LOCATION (#44), When I book, Then it is refused and names the clinic, and nothing is filed.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:79 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.1 `scheduler` Given a booked appointment, When I cancel it with a reason, Then the slot is open again and the appointment is marked cancelled by patient or clinic, with the reason.	written cloud-rpms spec/features/scheduler_day_spec.rb:291 (rpc, full, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:55 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_cancel_appointment_test.rb:59 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-02.2 `scheduler` Given a booked appointment, When I cancel it without saying whether the patient or the clinic cancelled, or without a reason, Then it is refused and the appointment stays booked.	partial lakeraven-ehr test/integration/scheduling_cancel_appointment_test.rb:86 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:87 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.3 `scheduler` Given cancellation remarks shorter than 3 or longer than 160 characters, When I save, Then it is refused.	partial lakeraven-ehr test/integration/scheduling_cancel_appointment_test.rb:99 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:93 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.4 `scheduler` Given reasons in CANCELLATION REASONS (#409.2) typed for the clinic, for the patient or for both, When I cancel on the clinic's behalf, Then only a reason typed clinic or both can be filed, and likewise patient or both when the patient cancelled.	partial lakeraven-ehr test/integration/scheduling_cancel_appointment_test.rb:69 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:99 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.5 `scheduler` Given an appointment the patient has already been checked in for, When I cancel it, Then it is refused; the check-in has to be undone first.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:81 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_cancel_appointment_test.rb:110 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:105 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.6 `scheduler` Given an appointment already cancelled or marked no-show, When I cancel it, Then it is refused.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:55 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_cancel_appointment_test.rb:110 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:111 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.7 `scheduler` Given a booked appointment, When I cancel it on the clinic's behalf with a reason and remarks, Then PATIENT (#2.98) holds the status cancelled by clinic, who cancelled it, when, the reason and the remarks, and the entry on the clinic in HOSPITAL LOCATION (#44.003) is gone so the slot counts as free.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:117 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.8 `scheduler` Given a booked appointment and an open slot in the same or another of my clinics, When I move it there with a cancellation type and reason, Then the original is cancelled in PATIENT (#2.98) with that type and reason and a remark that it was rescheduled to the new time, and a new appointment is filed at the new time in HOSPITAL LOCATION (#44.003) and PATIENT (#2.98) carrying the original's note.	partial lakeraven-ehr test/integration/live_scheduling_move_appointment_test.rb:26 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:68 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:82 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:155 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:172 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:182 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:123 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.9 `scheduler` Given an appointment that is checked in, cancelled or a no-show, When I try to move it, Then it is refused.	partial lakeraven-ehr test/integration/live_scheduling_move_appointment_test.rb:66 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:97 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:129 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.10 `scheduler` Given the new slot is full or blocked, When I move an appointment there, Then the overbook rules of S-SCH-01 apply, and when they refuse the original stays booked.	partial lakeraven-ehr test/integration/live_scheduling_move_appointment_test.rb:66 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:110 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:122 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:133 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:145 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:190 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_reschedule_appointment_test.rb:204 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:135 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.11 `scheduler` Given an appointment cancelled by the patient or by the clinic, When I undo the cancellation with an appointment length, Then PATIENT (#2.98) no longer holds a cancellation status, reason or canceller, and the appointment is on the clinic again in HOSPITAL LOCATION (#44.003) with that length.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:141 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.12 `scheduler` Given a cancelled appointment whose slot has since been filled, When I undo the cancellation, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:147 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.13 `scheduler` Given an appointment that is not cancelled, When I undo a cancellation, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:153 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.14 `scheduler` Given an appointment that is on neither the clinic in HOSPITAL LOCATION (#44.003) nor the patient in PATIENT (#2.98), When I cancel it, Then it is refused and nothing is filed.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:159 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-02.15 `scheduler` Given another user holds the lock on the patient's appointments in PATIENT (#2.98), When I cancel one, Then it is refused, I am told another user is working with this patient, and the appointment stays booked.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:165 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-03.1 `front_desk_clerk` Given a patient with an appointment today, When I check them in, Then the appointment shows checked in with the time, and a visit is created for the clinic and date.	written cloud-rpms spec/features/scheduler_day_spec.rb:307 (rpc, full, written; as PROFILE,REG) lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:81 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_checkin_appointment_test.rb:62 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_checkin_appointment_test.rb:128 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_checkin_appointment_test.rb:150 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG
S-SCH-03.2 `front_desk_clerk` Given a patient with an appointment today and a clinic with a default provider, When I check them in naming the provider, Then HOSPITAL LOCATION (#44.003) holds the check-in time, me as the user who checked in and when it was entered, and VISIT (#9000010) holds a visit for the patient at the clinic on that date with that provider.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:173 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-03.3 `front_desk_clerk` Given a check-in date that differs from the appointment's date, or lies in the future, When I save, Then it is refused and nothing is filed.	partial lakeraven-ehr test/integration/scheduling_checkin_appointment_test.rb:96 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:179 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-03.4 `front_desk_clerk` Given a clinic that requires a visit provider in CLINIC SETUP PARAMETERS (#9009017.2), When I check in without naming one, Then it is refused.	partial lakeraven-ehr test/integration/scheduling_checkin_appointment_test.rb:73 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:185 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-03.5 `front_desk_clerk` Given a clinic set up to use several clinic stop codes in CLINIC SETUP PARAMETERS (#9009017.2), When I check in without choosing a stop from CLINIC STOP (#40.7), Then it is refused; a clinic with one stop files its own.	partial lakeraven-ehr test/integration/live_scheduling_visit_day_test.rb:87 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_checkin_appointment_test.rb:170 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_checkin_appointment_test.rb:188 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:191 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-03.6 `front_desk_clerk` Given a patient whose health record number at this facility is a temporary one, When I check them in, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:197 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-03.7 `front_desk_clerk` Given an appointment already checked in, checked out, cancelled or marked no-show, When I check it in, Then it is refused.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:81 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_checkin_appointment_test.rb:108 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:203 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-03.8 `front_desk_clerk` Given a check-in with a routing slip asked for on a named printer, When I save, Then the routing slip for that patient and appointment prints to that device after the check-in is filed.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:209 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-03.9 `front_desk_clerk` Given a checked-in appointment, When I undo the check-in, Then HOSPITAL LOCATION (#44.003) no longer holds a check-in time or user and the appointment is scheduled again.	written cloud-rpms spec/features/scheduler_day_spec.rb:355 (rpc, full, written; as PROFILE,REG) lakeraven-ehr test/integration/live_scheduling_visit_day_test.rb:31 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:56 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:68 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:208 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG
S-SCH-03.10 `front_desk_clerk` Given two clinics of one division, each set to create a visit at check-in (CLINIC SETUP PARAMETERS #9009017.2, CREATE VISIT AT CHECK-IN?), and a patient with an appointment today at each, When I check the patient in at each clinic, Then each check-in leaves a VISIT (#9000010) whose HOSPITAL LOCATION is the clinic it was checked in at, so visits at the same division's clinics are told apart. (At the demo site: DEMO PRIMARY CARE and DEMO IHS CLINIC. It needs a BSDX resource per clinic and DEMO PRIMARY CARE creating a visit at check-in, rpms-ops#870.)	planned cloud-rpms spec/features/scheduler_spec.rb:75 (rpc, full, planned; as PROFILE,SCHED)	not run	not run
S-SCH-04.1 `scheduler` Given a clinic whose resource in BSDX RESOURCE (#9002018.1) has access blocks in BSDX ACCESS BLOCK (#9002018.3) over a week, When I search for slots of the clinic's appointment length between two dates, Then every slot returned starts inside one of those blocks on a day in the range, no earlier than the clinic's display start hour in HOSPITAL LOCATION (#44), ends within the block, and the block has fewer active appointments (scheduled, checked in or checked out) over that time than its slot count.	partial cloud-rpms spec/features/scheduler_day_spec.rb:232 (rpc, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:109 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_find_open_time_test.rb:69 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_find_open_time_test.rb:93 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/models/lakeraven/ehr/clinic_day_test.rb:60 (lakeraven-ehr, partial, written; as -)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-04.2 `scheduler` Given an access block whose access type in BSDX ACCESS TYPE (#9002018.35) prevents access, When I search, Then no slot inside it is returned.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:199 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_find_open_time_test.rb:102 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:217 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-04.3 `scheduler` Given a date in HOLIDAY (#40.5) and a clinic that does not schedule on holidays in HOSPITAL LOCATION (#44), When I search across it, Then no slot on that date is returned; a clinic that schedules on holidays returns its slots as usual.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:166 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_find_open_time_test.rb:117 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:223 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-04.4 `scheduler` Given dates beyond the clinic's maximum days for future booking, or inside its inactive period, in HOSPITAL LOCATION (#44), When I search, Then no slot on those dates is returned.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:166 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_find_open_time_test.rb:135 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:229 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-04.5 `scheduler` Given I restrict the search to mornings or to afternoons, When I search, Then only slots starting before noon, or from noon, are returned.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:109 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_find_open_time_test.rb:83 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/models/lakeraven/ehr/clinic_day_test.rb:71 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:235 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-04.6 `scheduler` Given I restrict the search to one access type, When I search, Then only slots in blocks of that type are returned.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:199 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_find_open_time_test.rb:155 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:241 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-04.7 `scheduler` Given a slot found by the search, When I pick it and name a registered patient, Then the appointment is filed as in S-SCH-01.1 at that time with the slot's length.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:109 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_find_open_time_test.rb:168 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:247 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-05.1 `scheduler` Given clinics whose resources name my user in BSDX RESOURCE USER (#9002018.15) at this facility, When I open the schedule, Then exactly those clinics are offered to me; holding SDZSUP, every clinic resource of the facility in BSDX RESOURCE (#9002018.1) is.	partial lakeraven-ehr test/integration/dashboard_counts_test.rb:54 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/dashboard_counts_test.rb:68 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_dashboard_counts_test.rb:29 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:255 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-05.2 `scheduler` Given a clinic's access blocks for the week in BSDX ACCESS BLOCK (#9002018.3) and a date in HOLIDAY (#40.5), When I view a day, Then each block shows with its access type and slot count, and the holiday shows as blocked for the whole day unless the clinic schedules on holidays in HOSPITAL LOCATION (#44).	partial lakeraven-ehr test/integration/live_scheduling_clinic_day_test.rb:29 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_clinic_day_test.rb:46 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_clinic_day_test.rb:56 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_clinic_day_test.rb:65 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:261 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-05.3 `scheduler` Given appointments of every status on a day, When I view the day, Then each shows with its status (scheduled, checked in, checked out, cancelled by clinic, cancelled by patient or no-show), and overbooks are marked.	partial lakeraven-ehr test/integration/dashboard_counts_test.rb:54 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_dashboard_counts_test.rb:29 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_clinic_day_test.rb:29 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_clinic_day_test.rb:73 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_clinic_day_test.rb:93 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:267 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-05.4 `scheduler` Given another user books, cancels or checks in an appointment on a clinic I am viewing, When they save, Then my view shows the change without my reloading it.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:273 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-05.5 `scheduler` Given today's appointments across several of my clinics, When I list them filtered to checked in, Then exactly those checked in and neither checked out nor cancelled are listed; and I can list today's, future, past or all appointments, sorted by appointment time, patient, check-in, check-out or no-show/cancel time.	partial lakeraven-ehr test/integration/live_scheduling_appointment_list_test.rb:28 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_list_test.rb:66 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_list_test.rb:74 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_list_test.rb:80 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_list_test.rb:97 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:279 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-05.6 `scheduler` Given a patient with appointments in several clinics, When I open that patient's appointments, Then every one is listed with its clinic and division, status, type (scheduled or walk-in), who made it and when, and its check-in, check-out and cancellation details, and I can act on those in my clinics.	partial cloud-rpms spec/features/scheduler_day_spec.rb:279 (rpc, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:134 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_patient_appointments_test.rb:49 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_patient_appointments_test.rb:65 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-05.7 `scheduler` Given a patient with past, today's and future appointments, When I list that patient's appointments for today, for the past or for the future, Then only those are listed, and a list with none says so.	partial lakeraven-ehr test/integration/live_scheduling_book_appointment_test.rb:134 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_patient_appointments_test.rb:77 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:285 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-06.1 `front_desk_clerk` Given a registered patient at the window with no appointment and a clinic I may modify appointments on, When I book a walk-in at the current time naming the provider and clinic stop, Then the appointment is on the clinic in HOSPITAL LOCATION (#44.003) and on the patient in PATIENT (#2.98) typed as a walk-in, checked in at that time by me, and VISIT (#9000010) holds the visit.	written cloud-rpms spec/features/scheduler_day_spec.rb:401 (rpc, full, written; as PROFILE,REG) lakeraven-ehr test/integration/live_scheduling_walk_in_test.rb:27 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_walk_in_test.rb:71 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_walk_in_test.rb:153 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_walk_in_test.rb:165 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG
S-SCH-06.2 `front_desk_clerk` Given the current slot is full or blocked, When I book the walk-in, Then the overbook rules of S-SCH-01 apply.	partial lakeraven-ehr test/integration/scheduling_walk_in_test.rb:86 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_walk_in_test.rb:98 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_walk_in_test.rb:179 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:293 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-06.3 `front_desk_clerk` Given a required check-in value missing (the provider when the clinic requires one, the stop when it uses several, the check-in time), When I save, Then it is refused and neither an appointment nor a visit is filed.	partial lakeraven-ehr test/integration/scheduling_walk_in_test.rb:110 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_walk_in_test.rb:131 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_walk_in_test.rb:140 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:299 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-06.4 `front_desk_clerk` Given the patient has an open entry on this clinic's wait list, When I book the walk-in and ask to take them off it, Then their entry in WAITING LIST (#9009017.11) is closed today with the resolution that an appointment was made.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:305 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-07.1 `front_desk_clerk` Given a checked-in appointment, When I check the patient out with the time, Then HOSPITAL LOCATION (#44.003) holds the check-out time, me as the user who checked out and when it was entered.	written cloud-rpms spec/features/scheduler_day_spec.rb:330 (rpc, full, written; as PROFILE,REG) lakeraven-ehr test/integration/live_scheduling_visit_day_test.rb:31 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:79 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:208 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG
S-SCH-07.2 `front_desk_clerk` Given an appointment that is not checked in, When I check it out, Then it is refused.	partial lakeraven-ehr test/integration/live_scheduling_visit_day_test.rb:31 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:96 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:313 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-07.3 `front_desk_clerk` Given a check-out date before the appointment's date or in the future, or a check-out time earlier than the check-in time on the same day, When I save, Then it is refused and nothing is filed.	partial lakeraven-ehr test/integration/scheduling_visit_day_test.rb:107 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:132 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:319 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-07.4 `front_desk_clerk` Given a check-out time more than five minutes ahead of the server's clock, When I save, Then it is refused; a time a few minutes ahead is filed as the server's current time.	partial lakeraven-ehr test/integration/scheduling_visit_day_test.rb:119 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:325 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-07.5 `front_desk_clerk` Given a patient who needs a follow-up and no slot to give them, When I check them out and add them to the clinic's wait list with a reason, priority and recall date, Then WAITING LIST (#9009017.1) for the clinic holds the patient (#9009017.11) with those values, today as the date added, me as the user who added them and the clinic's default provider.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:331 (bprm, full, owed; as PROFILE,REG)	not run	not run
S-SCH-07.6 `front_desk_clerk` Given a checked-out appointment, When I undo the check-out, Then HOSPITAL LOCATION (#44.003) no longer holds a check-out time or user and the appointment is checked in again.	written cloud-rpms spec/features/scheduler_day_spec.rb:343 (rpc, full, written; as PROFILE,REG) lakeraven-ehr test/integration/live_scheduling_visit_day_test.rb:31 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:143 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG
S-SCH-08.1 `scheduler` Given a scheduled appointment whose time has passed with no check-in, When I mark it a no-show with remarks, Then PATIENT (#2.98) holds the status no-show, me as who marked it, when, the clinic and the remarks, and the appointment no longer counts against the slot.	partial cloud-rpms spec/features/scheduler_day_spec.rb:370 (rpc, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_visit_day_test.rb:64 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:158 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:208 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-08.2 `scheduler` Given an appointment whose time has not yet passed, or one already checked in, cancelled or a no-show, When I mark it a no-show, Then it is refused.	partial lakeraven-ehr test/integration/live_scheduling_visit_day_test.rb:64 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:169 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:339 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-08.3 `scheduler` Given remarks shorter than 3 or longer than 160 characters, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:345 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-08.4 `scheduler` Given a no-show appointment, When I undo the no-show, Then PATIENT (#2.98) no longer holds the no-show status and the appointment is on the clinic again in HOSPITAL LOCATION (#44.003) with its length and note.	written cloud-rpms spec/features/scheduler_day_spec.rb:386 (rpc, full, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_visit_day_test.rb:64 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_visit_day_test.rb:181 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-08.5 `scheduler` Given a no-show appointment whose slot has since been filled, When I undo the no-show, Then it is refused.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:351 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-09.1 `scheduler` Given a booked appointment, When I change its note, Then HOSPITAL LOCATION (#44.003) holds the new note on that appointment and nothing else about it changes.	written cloud-rpms spec/features/scheduler_day_spec.rb:261 (rpc, full, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_appointment_details_test.rb:26 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_details_test.rb:54 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_details_test.rb:127 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-09.2 `scheduler` Given a note shorter than 2 or longer than 150 characters, or containing a semicolon or a colon, When I save, Then it is refused.	partial lakeraven-ehr test/integration/scheduling_appointment_details_test.rb:65 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:359 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-09.3 `scheduler` Given a cancelled or no-show appointment, When I change its remarks to between 3 and 160 characters, Then PATIENT (#2.98) holds the new remarks.	partial lakeraven-ehr test/integration/live_scheduling_appointment_details_test.rb:26 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_details_test.rb:76 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:365 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-09.4 `scheduler` Given a booked appointment on a clinic that allows variable appointment lengths in HOSPITAL LOCATION (#44), When I change its length, Then HOSPITAL LOCATION (#44.003) holds the new length and the start time is unchanged.	partial lakeraven-ehr test/integration/live_scheduling_appointment_details_test.rb:26 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_details_test.rb:93 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_appointment_details_test.rb:106 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:371 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-10.1 `scheduler` Given a patient who needs an appointment and a clinic with a wait list, When I add them with the date added, a reason, a priority, a provider, a recall date and comments, Then WAITING LIST (#9009017.1) for that clinic holds the patient (#9009017.11) with those values and me as the user who added them, and the reason is one typed for adding in WAITING LIST REASON (#9009017.4).	partial cloud-rpms spec/features/scheduler_day_spec.rb:426 (rpc, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_wait_list_test.rb:58 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_wait_list_test.rb:49 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-10.2 `scheduler` Given no patient, clinic, date added, reason or recall date, When I save, Then it is refused and nothing is filed.	partial lakeraven-ehr test/integration/scheduling_wait_list_test.rb:60 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:379 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-10.3 `scheduler` Given a clinic whose wait list is marked inactive in WAITING LIST (#9009017.1), When I add a patient, Then that clinic cannot be chosen.	partial lakeraven-ehr test/integration/scheduling_wait_list_test.rb:71 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:385 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-10.4 `scheduler` Given an open entry, When I change its reason, priority, provider, recall date or comments, Then the entry holds the new values and is still open.	partial lakeraven-ehr test/integration/scheduling_wait_list_test.rb:93 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:391 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-10.5 `scheduler` Given an open entry, When I remove it with the date removed and a resolution typed for removal in WAITING LIST REASON (#9009017.4), Then the entry holds that date, resolution and me as the user who removed it, and it is closed.	written cloud-rpms spec/features/scheduler_day_spec.rb:446 (rpc, full, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_scheduling_wait_list_test.rb:58 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_wait_list_test.rb:104 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-10.6 `scheduler` Given a removal without a date removed or a resolution, When I save, Then it is refused and the entry stays open.	partial lakeraven-ehr test/integration/scheduling_wait_list_test.rb:114 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:397 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-10.7 `scheduler` Given an open entry, When I book the patient from the wait list into a slot of that clinic, Then the appointment is filed as in S-SCH-01.1 and the entry is closed today with the resolution that an appointment was made and a comment naming the clinic and time.	partial lakeraven-ehr test/integration/live_scheduling_wait_list_test.rb:85 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:403 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-10.8 `scheduler` Given a closed entry, When I open the wait list, Then I can read and edit it but neither remove it nor book from it again.	partial lakeraven-ehr test/integration/scheduling_wait_list_test.rb:125 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:409 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-10.9 `scheduler` Given entries across my clinics, open and closed, When I list one clinic's wait list for a recall-date range, open only, Then exactly the open entries of that clinic with a recall date in the range are listed, in recall-date then priority order.	partial lakeraven-ehr test/integration/live_scheduling_wait_list_test.rb:58 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_wait_list_test.rb:141 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:415 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-11.1 `scheduler` Given a clinic whose pre-appointment letter in HOSPITAL LOCATION (#44) names a template in LETTER (#407.5), and patients with scheduled appointments in a date range, When I print the clinic's pre-appointment letters for that range, Then one letter per patient is produced with their name, address and health record number, the template's opening and closing text, and each of their appointments in the range with clinic and time; cancelled, no-show and checked-in appointments and deceased patients are left out.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:423 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-11.2 `scheduler` Given a template that greets the parents and a patient under 18, When I print, Then that patient's letter is addressed to their parents.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:429 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-11.3 `scheduler` Given appointments in the range cancelled by the clinic, cancelled by the patient, and marked no-show in PATIENT (#2.98), When I print letters of one of those three kinds, Then only the patients with appointments of that kind get a letter, on the clinic's template of that kind.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:435 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-11.4 `scheduler` Given a clinic with no template of the chosen kind in HOSPITAL LOCATION (#44) and none chosen by hand, or no appointments of that kind in the range, When I print, Then no letter is produced and I am told which of the two it was.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:441 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-11.5 `scheduler` Given one appointment that is scheduled, cancelled or a no-show, When I print its letter from the appointment, Then only that patient's letter of the matching kind is produced.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:447 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-12.1 `scheduler` Given I hold SDZSUP, When I add a letter with a name of 3 to 30 characters, one of the four kinds (pre-appointment, clinic cancellation, appointment cancellation, no-show), an opening and a closing text, and whether it greets the parents, Then LETTER (#407.5) holds it with those values.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:455 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-12.2 `scheduler` Given a name missing or outside 3 to 30 characters, or no kind, When I save, Then it is refused and nothing is filed.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:461 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-12.3 `scheduler` Given an existing letter, When I change its name, texts or the parents greeting, Then LETTER (#407.5) holds the new values and its kind is unchanged.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:467 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-12.4 `scheduler` Given I do not hold SDZSUP, When I open scheduling, Then I cannot add or change a letter template.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:473 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-13.1 `scheduler` Given appointments cancelled by the clinic and by the patient in my clinics over a range, When I run the cancelled appointment report for one of the two, Then it lists exactly the appointments in PATIENT (#2.98) cancelled that way in those clinics and dates, with the reason.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:481 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-13.2 `scheduler` Given no-shows in my clinics over a range, When I run the no-show report, as totals only or in full, Then it lists them, or counts them, by clinic.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:487 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-13.3 `scheduler` Given a clinic's appointments on a date, When I run the clinic schedule report for that date, one date per page or not, Then it lists the day's appointments in time order with each patient and status.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:493 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-13.4 `scheduler` Given a clinic's checked-in visits over a range, When I run the clinic workload report as a summary by month or a detail by day, with or without the previous year beside it, Then it counts the visits per clinic for each period.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:499 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-13.5 `scheduler` Given appointments past their time in my clinics with no check-in, check-out, cancellation or no-show recorded, When I run the appointments-requiring-action report over the range, Then exactly those are listed.	partial lakeraven-ehr test/integration/appointments_needing_action_test.rb:85 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:100 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:108 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:121 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:138 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:147 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:155 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:173 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:183 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:193 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:200 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_appointments_needing_action_test.rb:40 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_appointments_needing_action_test.rb:65 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:505 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-13.6 `scheduler` Given wait-list entries in my clinics, When I run the wait list report over a range of recall, added or removed dates, with or without removed entries, grouped by date, priority, provider, reason or resolution, for one priority or all, in full or as a summary, Then it lists or counts exactly the entries in WAITING LIST (#9009017.1) that match.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:511 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-13.7 `scheduler` Given a patient with future appointments, When I print their future appointments, or their routing slip, wrist band, medication profile or a wellness handout from an appointment, Then the printout is for that patient only.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:517 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-13.8 `scheduler` Given I hold neither SDZSUP nor SDZMENU, When I open reports, Then none of the scheduling reports is offered to me.	partial lakeraven-ehr test/integration/appointments_needing_action_test.rb:165 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/appointments_needing_action_test.rb:209 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/live_appointments_needing_action_test.rb:89 (lakeraven-ehr, partial, written; as PROFILE,MD) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:523 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-14.1 `scheduler` Given a clinic whose resource is in BSDX RESOURCE (#9002018.1), When I set its hours for chosen weekdays (a start time, an end time, the appointments each slot takes and an access type) from a first date through a last date, Then BSDX ACCESS BLOCK (#9002018.3) holds one block for each chosen day in that range with those values, and no day outside it changes.	written cloud-rpms spec/features/scheduler_day_spec.rb:201 (rpc, full, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_clinic_hours_test.rb:61 (lakeraven-ehr, partial, written; as PROFILE,SCHED)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED
S-SCH-14.2 `scheduler` Given hours set for a clinic, When a scheduler searches its open times or books it, Then the times offered are those blocks, the same in every interface that reads BSDX ACCESS BLOCK.	owed cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:531 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-14.3 `scheduler` Given an end time not after the start time, fewer than one appointment per slot, no access type or an inactive one, or a last date before the first, When I save, Then it is refused, names the value, and nothing is filed.	partial lakeraven-ehr test/integration/scheduling_clinic_hours_test.rb:83 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:537 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-14.4 `scheduler` Given a day in the range that already has blocks, When I set hours over it again, Then its old blocks are replaced by the new ones, not added to.	partial lakeraven-ehr test/integration/scheduling_clinic_hours_test.rb:74 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:543 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-14.5 `scheduler` Given an active appointment (not cancelled, not a no-show) on a day whose blocks I would replace, at a time the new hours no longer cover, When I save, Then it is refused and names that appointment's date and time, and the blocks and the appointment are unchanged. (BSDX CANCEL AV BY DATE does not check: `AVDELDT^BSDX13` deletes every block in the range, and its appointment check `APTINBLK` is commented out as not called in the current version.)	partial lakeraven-ehr test/integration/scheduling_clinic_hours_test.rb:103 (lakeraven-ehr, partial, written; as PROFILE,SCHED) lakeraven-ehr test/integration/scheduling_clinic_hours_test.rb:115 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:549 (bprm, full, owed; as PROFILE,SCHED)	not run	not run
S-SCH-14.6 `scheduler` Given I hold neither SDZSUP nor SDZMENU, When I open scheduling, Then I cannot set a clinic's hours.	partial lakeraven-ehr test/integration/scheduling_clinic_hours_test.rb:138 (lakeraven-ehr, partial, written; as PROFILE,SCHED) cloud-rpms spec/scenarios/phase1/w02_scheduling_spec.rb:555 (bprm, full, owed; as PROFILE,SCHED)	not run	not run

W03 Pre-Visit / Triage (MA and nurse)

Journeys: clinician-signs-on-and-finds-patient.bpmn, patient-is-roomed.bpmn.

26 scenarios

Scenario	Test	Analyst	Automated
S-SGN-01.1 `medical_assistant` Given valid access and verify codes, When I sign on, Then the EHR opens on Notifications and shows my name and my division.	partial cloud-rpms spec/features/clinical_staff_spec.rb:58 (rpc, partial, written; as PROFILE,MA) cloud-rpms spec/features/clinical_staff_spec.rb:71 (rpc, partial, written; as PROFILE,RN) cloud-rpms spec/features/clinical_staff_spec.rb:84 (rpc, partial, written; as PROFILE,MD) cloud-rpms spec/features/front_desk_clerk_spec.rb:43 (rpc, partial, written; as PROFILE,REG) cloud-rpms spec/features/scheduler_spec.rb:46 (rpc, partial, written; as PROFILE,SCHED) cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:18 (vuecentric, full, planned; as PROFILE,MA) cloud-rpms spec/features/vuecentric/nurse_spec.rb:16 (vuecentric, full, planned; as PROFILE,RN) cloud-rpms spec/features/vuecentric/provider_spec.rb:16 (vuecentric, full, planned; as PROFILE,MD)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,REG, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,SCHED, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,MA, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,RN, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,MD
S-SGN-01.2 `medical_assistant` Given a wrong verify code, When I sign on, Then sign-on is refused with a message and no part of the chart opens.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:21 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-SGN-01.3 `medical_assistant` Given a verify code that has expired, When I sign on, Then I am made to choose a new one before the chart opens.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:24 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-SGN-02.1 `nurse` Given a notification addressed to me, When I sign on, Then it is listed on the Notifications tab with its patient, and opening it puts that patient in context.	partial lakeraven-ehr test/integration/live_notifications_test.rb:40 (lakeraven-ehr, partial, written; as PROFILE,MD) lakeraven-ehr test/integration/notifications_test.rb:34 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/features/vuecentric/provider_spec.rb:22 (vuecentric, partial, planned; as PROFILE,MD)	not run	not run
S-SGN-02.2 `nurse` Given a notification addressed to me that RPMS lists as one I can delete, When I remove it, Then it is no longer listed, and my count of notifications is one fewer.	partial lakeraven-ehr test/integration/live_notification_actions_test.rb:57 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/notification_actions_test.rb:102 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/notification_actions_test.rb:118 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w03_pre_visit_triage_ma_and_nurse_spec.rb:7 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-SGN-02.3 `nurse` Given a notification addressed to me that RPMS lists as one I cannot delete, When I look at it, Then it offers no way to remove it, and it stays listed until the work it asks for is done.	partial lakeraven-ehr test/integration/live_notification_actions_test.rb:57 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/notification_actions_test.rb:129 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w03_pre_visit_triage_ma_and_nurse_spec.rb:13 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-SGN-02.4 `nurse` Given a notification addressed to me, When I forward it to a colleague I find by name, with a comment, Then it is listed in my colleague's notifications with its patient, my comment shows with it, and my own copy stays listed.	partial lakeraven-ehr test/integration/live_notification_actions_test.rb:84 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/notification_actions_test.rb:174 (lakeraven-ehr, partial, written; as -) lakeraven-ehr test/integration/notification_actions_test.rb:200 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w03_pre_visit_triage_ma_and_nurse_spec.rb:19 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-TRI-01.1 `medical_assistant` Given a patient checked in to my clinic, When I open Patient Select and choose the clinic, Then the patient is listed with the appointment time and opening them shows the Cover Sheet.	partial cloud-rpms spec/features/clinical_staff_spec.rb:58 (rpc, partial, written; as PROFILE,MA) rpms-ops test/persona_walk.rb (rpc, partial, written; as PROFILE,MA) rpms-ops test/persona_walk.rb (rpc, partial, written; as PROFILE,RN) cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:29 (vuecentric, full, planned; as PROFILE,MA)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,MA, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,RN, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,MA
S-TRI-01.2 `medical_assistant` Given a patient with no appointment today, When I choose them from the list of all patients, Then opening them shows the Cover Sheet, with no visit in context until I select or create one.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:32 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-02.1 `medical_assistant` Given the patient's visit is selected, When I enter the measurements and save, Then they are filed on the visit (V MEASUREMENT) and show on the Vitals tab and the Cover Sheet.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:37 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-02.2 `medical_assistant` Given a value out of range (a BP of 400), When I save, Then I am asked to confirm or correct it.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:40 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-02.3 `medical_assistant` Given the patient's visit is selected, When I add a screening measurement (a PHQ-2 score) in vitals entry and save, Then it is filed on the visit in V MEASUREMENT (#9000010.01) and shows with the other vitals.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:44 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-03.1 `nurse` Given a selected visit, When I record the chief complaint and a screening result on the Wellness tab, Then both are filed on the visit and the screening's reminder is satisfied.	partial rpms-ops test/persona_walk.rb (rpc, partial, written; as PROFILE,RN) cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:88 (vuecentric, partial, planned; as PROFILE,MA) cloud-rpms spec/features/vuecentric/nurse_spec.rb:27 (vuecentric, partial, planned; as PROFILE,RN)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,RN
S-TRI-04.1 `medical_assistant` Given a patient with an allergy on file, When I review it with the patient and mark it reviewed, Then the review is recorded on the visit.	partial cloud-rpms spec/features/clinical_staff_spec.rb:58 (rpc, partial, written; as PROFILE,MA) rpms-ops test/persona_walk.rb (rpc, partial, written; as PROFILE,MA) cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:49 (vuecentric, full, planned; as PROFILE,MA)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,MA, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,MA
S-TRI-04.2 `medical_assistant` Given a patient who reports a new allergy, When I add it, Then it shows on the Cover Sheet's allergies.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:52 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-05.1 `medical_assistant` Given a medication the patient takes from outside the clinic, When I add it as an outside medication, Then it shows on the Medications tab for the provider to reconcile.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:57 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-06.1 `medical_assistant` Given a patient checked in today, When I open the encounter dialog, Then today's visit for my clinic is offered first, and selecting it shows it in the chart header.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:62 (vuecentric, full, planned; as PROFILE,MA) cloud-rpms spec/features/vuecentric/nurse_spec.rb:21 (vuecentric, full, planned; as PROFILE,RN)	not run	not run
S-TRI-06.2 `medical_assistant` Given no visit selected, When I try to enter vitals, Then I am asked to select a visit first.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:65 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-06.3 `medical_assistant` Given a walk-in with no visit today, When I create a visit for my clinic and now, with the provider who will see the patient as primary, Then VISIT (#9000010) holds it with that provider primary in V PROVIDER (#9000010.06), and it is in context.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:69 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-09.1 `nurse` Given a selected visit, When I add a health factor from its category, Then V HEALTH FACTORS (#9000010.23) holds it on the visit with me as the user who entered it.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:99 (vuecentric, full, planned; as PROFILE,MA) cloud-rpms spec/features/vuecentric/nurse_spec.rb:45 (vuecentric, full, planned; as PROFILE,RN)	not run	not run
S-TRI-10.1 `nurse` Given a selected visit, When I record a PPD placed with its site, volume, date applied and myself as administering it, Then V SKIN TEST (#9000010.12) holds it on the visit with its result pending, and the placement's CPT is filed in V CPT (#9000010.18).	planned cloud-rpms spec/features/vuecentric/nurse_spec.rb:50 (vuecentric, full, planned; as PROFILE,RN)	not run	not run
S-TRI-12.1 `nurse` Given a selected visit and the provider who orders the test, When I enter a point-of-care result with a sign or symptom and save, Then ORDER (#100) holds the test ordered by that provider, and V LAB (#9000010.09) holds the result once on the visit, flagged against its reference range.	planned cloud-rpms spec/features/vuecentric/nurse_spec.rb:61 (vuecentric, full, planned; as PROFILE,RN)	not run	not run
S-TRI-07.1 `medical_assistant` Given today's visit is selected, When I pick a chief complaint and save, Then it is filed on the visit in V NARRATIVE TEXT (#9000010.34) with the type CHIEF COMPLAINT, and shows on the Triage Summary.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:74 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-07.2 `medical_assistant` Given a chief complaint entered in error, When I delete it, Then it is no longer filed on the visit.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:77 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-08.1 `nurse` Given vitals and a chief complaint filed on today's visit, When I open the triage summary, Then it shows today's vitals and the chief complaint, with who entered it.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:82 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-TRI-08.2 `nurse` Given a visit with nothing recorded yet, When I open the triage summary, Then it shows that nothing is recorded, not another visit's data.	owed cloud-rpms spec/scenarios/phase1/w03_pre_visit_triage_ma_and_nurse_spec.rb:27 (vuecentric, full, owed; as PROFILE,RN)	not run	not run

W04 Provider/MA Visit, Encounter and Note-Taking

Journeys: clinician-sees-the-patient.bpmn.

43 scenarios

Scenario	Test	Analyst	Automated
S-SGN-03.1 `provider` Given a patient with active problems, medications and an allergy, When I select the patient, Then the Cover Sheet shows each of them, and today's vitals once they are taken.	partial cloud-rpms spec/features/clinical_staff_spec.rb:84 (rpc, partial, written; as PROFILE,MD) rpms-ops test/persona_walk.rb (rpc, partial, written; as PROFILE,MD) cloud-rpms spec/features/vuecentric/provider_spec.rb:27 (vuecentric, full, planned; as PROFILE,MD)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,MD, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, rpc as PROFILE,MD
S-CHT-01.1 `provider` Given a patient in PATIENT (#2) with a health record number at this facility, When I search by last name, by health record number, by date of birth, or by the last four digits of the social security number (alone, or after the first letter of the last name), Then each search lists the patient with name, date of birth, sex and health record number, and never the full social security number.	partial lakeraven-ehr test/integration/live_patient_bar_search_test.rb:44 (lakeraven-ehr, partial, written; as PROFILE,MD) lakeraven-ehr test/integration/patient_bar_search_test.rb:45 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:7 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-CHT-01.2 `provider` Given I have opened other patients' charts before, When I am on the empty search with nothing typed, Then my recent patients are listed, the most recent first, and opening one opens their chart; another user on the same workstation does not see my list.	partial lakeraven-ehr test/integration/live_patient_bar_search_test.rb:62 (lakeraven-ehr, partial, written; as PROFILE,MD) lakeraven-ehr test/integration/patient_bar_search_test.rb:72 (lakeraven-ehr, partial, written; as -) cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:13 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-CHT-01.3 `provider` Given a patient with an allergy in PATIENT ALLERGIES (#120.8) and an active flag in PRF ASSIGNMENT (#26.13), When I open their chart, Then a banner shows the name together with the date of birth and the health record number, the allergy and the flag, and the patient's own navigation appears beside it.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:19 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-CHT-01.4 `provider` Given a patient whose record is marked sensitive in DG SECURITY LOG (#38.1), When I choose them from the search or my recent patients, Then I see the sensitive-record warning before any of the chart is shown, and the rules of S-REG-04 apply: accepting opens the chart and logs my access in DG SECURITY LOG (#38.1), declining opens nothing and logs nothing.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:25 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-CHT-01.5 `provider` Given a patient's chart is open, When I close the chart, or switch patient and pick another, Then the first patient's banner and navigation are gone, and either the empty search is shown or the new patient's chart opens with their own banner.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:31 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-CHT-01.6 `provider` Given a patient's chart is open, When a request names another patient, or a patient identifier that is not in PATIENT (#2), Then the screen shows the patient the request names, with nothing of the first patient on it, or says there is no such patient and opens no chart.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:37 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-CHT-01.7 `provider` Given a patient's chart is open, When I move to any screen of the chart, Then the patient bar stays in view with the patient's picture (their photo where RPMS holds one, otherwise their initials), name, age and sex, and with no patient open the same place holds the search.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:43 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-CHT-01.8 `provider` Given the patient is with me and their chart is open, When I open the verifying details from the patient bar, Then I see what confirms who is in front of me (full date of birth, health record number, address and phone, and the last four digits of the social security number only if I hold AGZVIEWSSN), they close again when I leave the bar or after a short time, and opening them is recorded in the audit trail under my name.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:49 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-CHT-01.9 `provider` Given a patient's chart is open, When I search for another patient from the patient bar, Then I can find them as in S-CHT-01.1 without first closing the chart, and opening them switches the chart as in S-CHT-01.5.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:55 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-VIS-01.1 `provider` Given a checked-in appointment, When I open the encounter dialog, Then today's visit for that clinic is offered and selecting it puts it in context.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:32 (vuecentric, full, planned; as PROFILE,MD)	not run	not run
S-VIS-01.2 `provider` Given a walk-in with no appointment, When I create a visit for my clinic and now, Then a new visit exists and is in context.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:63 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-VIS-02.1 `provider` Given a patient with active problems, When I select a problem as a POV, Then a V POV entry exists on the visit with the problem's code.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:71 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-VIS-02.2 `provider` Given a new diagnosis, When I add it as a problem and a POV, Then it is on the problem list and on the visit.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:38 (vuecentric, full, planned; as PROFILE,MD)	not run	not run
S-VIS-02.3 `provider` Given a new diagnosis, When I add it as a problem and do not use it as a POV, Then it is on the problem list (PROBLEM, #9000011) and no V POV (#9000010.07) is filed for it on the visit.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:41 (vuecentric, full, planned; as PROFILE,MD)	not run	not run
S-VIS-03.1 `provider` Given a visit in context, When I pick a quick order and sign it, Then the order is active on the Orders tab.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:47 (vuecentric, partial, planned; as PROFILE,MD)	not run	not run
S-VIS-03.2 `provider` Given a visit in context, When I enter an outpatient medication with dose, route, schedule, days supply, quantity and refills, accept it, and sign it later together with the note, Then ORDER (#100) holds it unsigned until then, and signing the note and the orders together releases it.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:50 (vuecentric, full, planned; as PROFILE,MD)	not run	not run
S-VIS-04.1 `provider` Given a visit in context, When I pick a note title, fill the template and sign with my electronic signature, Then the note is signed (TIU DOCUMENT) and linked to the visit.	planned cloud-rpms spec/features/vuecentric/nurse_spec.rb:40 (vuecentric, full, planned; as PROFILE,RN) cloud-rpms spec/features/vuecentric/provider_spec.rb:56 (vuecentric, full, planned; as PROFILE,MD)	not run	not run
S-VIS-04.2 `provider` Given a wrong electronic signature code, When I sign, Then the note stays unsigned and I am told why.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:59 (vuecentric, full, planned; as PROFILE,MD)	not run	not run
S-VIS-05.1 `medical_assistant` Given a visit in context, When I record an immunization with lot and site, Then it is filed on the visit and on the patient's immunization history.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:112 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-VIS-06.1 `provider` Given clinic and outside medications on the Medications tab, When I mark each continued, changed or stopped, Then the list shows the result and the reconciliation is recorded on the visit.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:79 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-VIS-07.1 `medical_assistant` Given a visit in context, When I pick a quick-note title, complete its template and sign with my electronic signature, Then TIU DOCUMENT (#8925) holds the note signed and linked to the visit.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:104 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-VIS-07.2 `medical_assistant` Given a quick note I have written, When I cancel the signature, Then the note is saved unsigned on the visit and stays on my list of unsigned notes.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:107 (vuecentric, full, planned; as PROFILE,MA)	not run	not run
S-VIS-08.1 `provider` Given a chief complaint, vitals, education, exams, health factors and reproductive factors filed on today's visit by others, When I open the visit, Then each shows with who entered it, and nothing from another visit.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:65 (vuecentric, full, planned; as PROFILE,MD)	not run	not run
S-WCC-01.1 `provider` Given a child with heights and weights on file, When I open the growth charts, Then each measurement from V MEASUREMENT (#9000010.01) is plotted at the child's age against the curves for the child's sex, and the table view lists the same values.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:87 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-WCC-01.2 `provider` Given a child with no measurement of one kind (head circumference), When I open that chart, Then the chart is empty and says so, rather than showing another child's data.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:93 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-WCC-01.3 `provider` Given a patient older than 21, When I open the Well Child tab, Then no growth chart is drawn and I am told the patient must be 21 or younger.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:99 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-WCC-02.1 `provider` Given a child at a well-child visit, When I open the well-child reminders, Then the exams, screenings and education due at the child's age are listed, and those already done are not listed as due.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:107 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-WCC-03.1 `nurse` Given a child at a well-child visit, When I open the education list, Then the topics due for the child's age are listed, and topics already documented are marked done.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:115 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-WCC-03.2 `nurse` Given I document a topic as given, with the parent's level of understanding, When I save, Then it is filed on the visit in V PATIENT ED (#9000010.16).	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:121 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-WH-01.1 `nurse` Given a patient, When I record gravida, full-term, premature, ectopic and multiple births, living children and the last menstrual period, and save, Then they are on file for the patient in REPRODUCTIVE FACTORS with today's date.	planned cloud-rpms spec/features/vuecentric/nurse_spec.rb:55 (vuecentric, full, planned; as PROFILE,RN)	not run	not run
S-WH-01.2 `nurse` Given a value that cannot be true (more full-term births than gravida), When I save, Then it is refused and names the value.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:129 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-WH-01.3 `nurse` Given a patient who is breastfeeding, When I record her lactation status, Then it is on file for the patient with today's date.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:135 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-WH-02.1 `nurse` Given a patient, When I record a contraception method with its start date, Then it is listed as current.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:143 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-WH-02.2 `nurse` Given a current method, When I record its end date, Then it is no longer listed as current and its history is kept.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:149 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-PRG-01.1 `provider` Given a pregnant patient, When I add a problem to the pregnancy issues list, Then it is listed for the current pregnancy and is on the patient's integrated problem list (PROBLEM #9000011).	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:157 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-PRG-01.2 `provider` Given the pregnancy's definitive estimated date of delivery, When I record it, Then it is on file for the pregnancy and shown on the list.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:163 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-PRG-01.3 `provider` Given a pregnancy problem addressed today, When I set it as a purpose of visit, Then it is filed as a POV (V POV #9000010.07) on today's visit.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:169 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-PRG-01.4 `provider` Given a problem added in error, When I delete it from the pregnancy list, Then I am asked whether to remove it from the problem list too, and the chosen record is removed.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:175 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-PRG-01.5 `provider` Given a male patient, When I open the Pregnancy tab, Then no pregnancy list is offered, and I am told the patient must be female.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:181 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-PRG-01.6 `provider` Given the prenatal pick list (on the Women's Health tab), When I pick a problem from it for a pregnant patient, Then it is added to the current pregnancy's list.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:187 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-PRG-02.1 `nurse` Given a child 5 years old or younger at a visit, When I record the feeding choice and save, Then it is filed on the visit.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:195 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-PRG-02.2 `nurse` Given a patient older than 5, When I open infant feeding, Then no entry can be made.	owed cloud-rpms spec/scenarios/phase1/w04_provider_ma_visit_encounter_and_note_taking_spec.rb:201 (vuecentric, full, owed; as PROFILE,RN)	not run	not run

W05 Diagnosis and Procedure Coding

Journeys: visit-is-billed.bpmn.

9 scenarios

Scenario	Test	Analyst	Automated
S-COD-01.1 `provider` Given a signed note, When I choose the E&M level on the visit, Then a V CPT entry with the E&M code exists on the visit.	owed cloud-rpms spec/scenarios/phase1/w05_diagnosis_and_procedure_coding_spec.rb:7 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-COD-02.1 `coder` Given a signed, coded visit, When I change a POV's ICD-10 code, Then the visit shows the corrected code and who changed it.	owed cloud-rpms spec/scenarios/phase1/w05_diagnosis_and_procedure_coding_spec.rb:15 (vuecentric, full, owed; as -)	not run	not run
S-COD-03.1 `coder` Given the stack's build, When I look up a code added in this fiscal year's update, Then it is found and active.	owed cloud-rpms spec/scenarios/phase1/w05_diagnosis_and_procedure_coding_spec.rb:23 (vuecentric, full, owed; as -)	not run	not run
S-COD-04.1 `provider` Given today's visit, When I choose new or established patient and the level of service, and save, Then the matching E&M code is filed on the visit in V CPT (#9000010.18).	owed cloud-rpms spec/scenarios/phase1/w05_diagnosis_and_procedure_coding_spec.rb:31 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-COD-04.2 `provider` Given a visit dated after a code was retired (99201, retired January 2021), When I open the E&M tool, Then the retired code is not offered.	owed cloud-rpms spec/scenarios/phase1/w05_diagnosis_and_procedure_coding_spec.rb:37 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-SRV-01.1 `provider` Given today's visit and the clinic's superbill, When I pick services and save, Then each is filed on the visit in V CPT (#9000010.18).	owed cloud-rpms spec/scenarios/phase1/w05_diagnosis_and_procedure_coding_spec.rb:45 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-SRV-02.1 `coder` Given a visit, When I add a CPT code with a modifier, a quantity and an associated diagnosis, and save, Then the V CPT entry on the visit holds the code, modifier, quantity and diagnosis.	owed cloud-rpms spec/scenarios/phase1/w05_diagnosis_and_procedure_coding_spec.rb:53 (vuecentric, full, owed; as -)	not run	not run
S-SRV-02.2 `coder` Given a procedure added in error, When I delete it, Then it is no longer on the visit.	owed cloud-rpms spec/scenarios/phase1/w05_diagnosis_and_procedure_coding_spec.rb:59 (vuecentric, full, owed; as -)	not run	not run
S-SRV-03.1 `nurse` Given today's visit, When I record the activity, the encounter time and the travel time, and save, Then they are on file for the visit.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:76 (vuecentric, partial, planned; as PROFILE,MD)	not run	not run

W06 After-Visit Summary and Care Plan

Journeys: visit-summary-is-given.bpmn.

4 scenarios

Scenario	Test	Analyst	Automated
S-AVS-01.1 `provider` Given a signed visit, When I print the after-visit summary, Then it lists the visit's POVs, current medications, today's orders and the next appointment.	owed cloud-rpms spec/scenarios/phase1/w06_after_visit_summary_and_care_plan_spec.rb:7 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-AVS-02.1 `nurse` Given a visit in context, When I record an education topic with the patient's understanding, Then a V PATIENT ED entry is on the visit and on the summary.	planned cloud-rpms spec/features/vuecentric/medical_assistant_spec.rb:93 (vuecentric, partial, planned; as PROFILE,MA) cloud-rpms spec/features/vuecentric/nurse_spec.rb:33 (vuecentric, full, planned; as PROFILE,RN)	not run	not run
S-AVS-03.1 `patient` Given a visit with a care plan recorded, When I am handed the summary, Then the care plan's goals and follow-up are on it in plain language.	owed cloud-rpms spec/scenarios/phase1/w06_after_visit_summary_and_care_plan_spec.rb:15 (-, full, owed; as -)	not run	not run
S-AVS-04.1 `provider` Given a visit in context, When I add a goal with its type, reason, start date and follow-up date, Then PATIENT GOALS (#9000093) holds it active for the patient.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:81 (vuecentric, full, planned; as PROFILE,MD)	not run	not run

W07 Reporting (limited)

Journeys: report-is-run.bpmn.

2 scenarios

Scenario	Test	Analyst	Automated
S-RPT-01.1 `site_manager` Given visits filed over a week, When I run the visit report for that week, Then the counts per clinic and provider match the visits in VISIT (#9000010).	owed cloud-rpms spec/scenarios/phase1/w07_reporting_limited_spec.rb:7 (terminal, full, owed; as -)	not run	not run
S-RPT-02.1 `site_manager` Given a visit with an unsigned note, When I run the incomplete visits report, Then that visit is on it with the provider's name.	owed cloud-rpms spec/scenarios/phase1/w07_reporting_limited_spec.rb:15 (terminal, full, owed; as -)	not run	not run

W08 Billing and Revenue Cycle (Medicare and Medicaid)

Journeys: visit-is-billed.bpmn.

4 scenarios

Scenario	Test	Analyst	Automated
S-BIL-01.1 `billing_technician` Given a coded visit for a patient with Medicaid eligibility on the visit date, When claims are generated, Then a claim for Medicaid exists for that visit with its CPT and ICD codes.	written cloud-rpms spec/features/billing_technician_spec.rb:37 (terminal, full, written; as PROFILE,BILL) rpms-ops test/persona_walk.rb (terminal, partial, written; as PROFILE,BILL)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, terminal as PROFILE,BILL, pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, terminal as PROFILE,BILL
S-BIL-02.1 `billing_technician` Given a claim with no errors, When I approve it, Then a bill exists with a bill number and the claim is closed.	partial rpms-ops test/persona_walk.rb (terminal, partial, written; as PROFILE,BILL) cloud-rpms spec/scenarios/phase1/w08_billing_and_revenue_cycle_medicare_and_medicaid_spec.rb:7 (terminal, full, owed; as -)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, terminal as PROFILE,BILL
S-BIL-02.2 `billing_technician` Given a claim with an error (a missing provider NPI), When I try to approve it, Then approval is refused and the error is named.	owed cloud-rpms spec/scenarios/phase1/w08_billing_and_revenue_cycle_medicare_and_medicaid_spec.rb:13 (terminal, full, owed; as -)	not run	not run
S-BIL-03.1 `billing_technician` Given approved Medicaid bills, When I export them, Then an 837P file is written with one claim per bill.	partial rpms-ops test/persona_walk.rb (terminal, partial, written; as PROFILE,BILL) cloud-rpms spec/scenarios/phase1/w08_billing_and_revenue_cycle_medicare_and_medicaid_spec.rb:21 (terminal, full, owed; as -)	not run	pass 2026-11-09 on bcer-9.0-20261109-d3adcff-ydb, terminal as PROFILE,BILL

W09 Credentialing (limited)

Journeys: provider-is-credentialed.bpmn.

3 scenarios

Scenario	Test	Analyst	Automated
S-CRD-01.1 `credentialing_coordinator` Given a new provider, When I create the user with a person class and the PROVIDER key, Then they can sign on to VueCentric, and appear as a selectable provider on a visit.	owed cloud-rpms spec/scenarios/phase1/w09_credentialing_limited_spec.rb:7 (terminal, full, owed; as -)	not run	not run
S-CRD-02.1 `credentialing_coordinator` Given a licence expiring in 30 days, When I run the expiring credentials report, Then that provider and licence are on it.	owed cloud-rpms spec/scenarios/phase1/w09_credentialing_limited_spec.rb:15 (terminal, full, owed; as -)	not run	not run
S-CRD-04.1 `provider` Given a new provider user, When I set my electronic signature code, Then signing a note with it succeeds and the note shows my signature block.	owed cloud-rpms spec/scenarios/phase1/w09_credentialing_limited_spec.rb:23 (vuecentric, full, owed; as PROFILE,MD)	not run	not run

W10 Prescriptions (Rx)

Journeys: prescription-is-filled.bpmn.

2 scenarios

Scenario	Test	Analyst	Automated
S-RX-01.1 `provider` Given a signed outpatient medication order, When the pharmacist verifies and dispenses it, Then a prescription exists and shows active on the Medications tab.	owed cloud-rpms spec/scenarios/phase2/w10_prescriptions_rx_spec.rb:7 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-RX-02.1 `pharmacist` Given a pending order for a patient with an allergy to the drug's class, When I verify it, Then the allergy check stops me until I document an override.	owed cloud-rpms spec/scenarios/phase2/w10_prescriptions_rx_spec.rb:15 (terminal, full, owed; as -)	not run	not run

W11 Lab Orders and Results

Journeys: lab-is-resulted.bpmn.

3 scenarios

Scenario	Test	Analyst	Automated
S-LAB-01.1 `provider` Given a signed lab order, When the lab verifies the result, Then it shows on the Labs tab and I get a notification.	owed cloud-rpms spec/scenarios/phase2/w11_lab_orders_and_results_spec.rb:7 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-LAB-02.1 `lab_technician` Given a signed lab order, When I accession it and verify a result, Then the result is filed on the patient and the order is complete.	owed cloud-rpms spec/scenarios/phase2/w11_lab_orders_and_results_spec.rb:15 (terminal, full, owed; as -)	not run	not run
S-LAB-03.1 `provider` Given a verified abnormal result, When I open the Labs tab, Then the result is flagged abnormal with its reference range.	owed cloud-rpms spec/scenarios/phase2/w11_lab_orders_and_results_spec.rb:23 (vuecentric, full, owed; as PROFILE,MD)	not run	not run

W12 Referrals and Consults

Journeys: consult-is-completed.bpmn.

5 scenarios

Scenario	Test	Analyst	Automated
S-REF-01.1 `provider` Given a consult I ordered, When the consultant completes it, Then it shows complete on the Consults tab with the report attached.	owed cloud-rpms spec/scenarios/phase2/w12_referrals_and_consults_spec.rb:7 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-REF-01.2 `provider` Given a visit in context, When I order a consult to a service with its urgency and the reason for the request, and sign it, Then REQUEST/CONSULTATION (#123) holds it for the patient, pending at that service.	planned cloud-rpms spec/features/vuecentric/provider_spec.rb:70 (vuecentric, full, planned; as PROFILE,MD)	not run	not run
S-REF-02.1 `prc_clerk` Given a consult to a service the clinic does not have, When I record the referral, Then a referral exists with the outside provider and the reason.	owed cloud-rpms spec/scenarios/phase2/w12_referrals_and_consults_spec.rb:15 (terminal, full, owed; as -)	not run	not run
S-REF-02.2 `prc_clerk` Given a referral I recorded, When I change its vendor or the facility referred to, Then REFERRAL (#90001) holds the new vendor or facility for that referral.	owed cloud-rpms spec/scenarios/phase2/w12_referrals_and_consults_spec.rb:21 (terminal, full, owed; as -)	not run	not run
S-REF-03.1 `nurse` Given an open consult with a report received, When I attach it and complete the consult, Then the consult shows complete and the provider is notified.	owed cloud-rpms spec/scenarios/phase2/w12_referrals_and_consults_spec.rb:29 (vuecentric, full, owed; as PROFILE,RN)	not run	not run

W13 PRC (Purchased/Referred Care)

Journeys: prc-is-authorized.bpmn.

3 scenarios

Scenario	Test	Analyst	Automated
S-PRC-01.1 `prc_clerk` Given a referral for an eligible patient, When I approve it, Then a PRC document exists with an obligated amount.	owed cloud-rpms spec/scenarios/phase2/w13_prc_purchased_referred_care_spec.rb:7 (terminal, full, owed; as -)	not run	not run
S-PRC-01.2 `prc_clerk` Given a referral waiting for my PRC decision, When I open it to decide, Then I see what the decision needs from the chart (the reason for referral, its diagnoses, and the documents attached to it, such as labs, imaging and the history and physical), and nothing else of the patient's chart: no behavioral health notes, no unrelated conditions, and nothing for a patient with no active referral.	owed cloud-rpms spec/scenarios/phase2/w13_prc_purchased_referred_care_spec.rb:13 (terminal, full, owed; as -)	not run	not run
S-PRC-02.1 `prc_clerk` Given an approved referral, When I issue the purchase order, Then it has a number and the funds are obligated.	owed cloud-rpms spec/scenarios/phase2/w13_prc_purchased_referred_care_spec.rb:21 (terminal, full, owed; as -)	not run	not run

W14 Patient Messaging and Communication

Journeys: patient-message-is-answered.bpmn.

2 scenarios

Scenario	Test	Analyst	Automated
S-MSG-01.1 `nurse` Given a message from a patient, When I reply, Then the patient sees the reply and the exchange is recorded in the chart.	owed cloud-rpms spec/scenarios/phase2/w14_patient_messaging_and_communication_spec.rb:7 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-MSG-02.1 `patient` Given a patient with a portal account, When I send a message, Then the clinic receives it and I see it in my sent messages.	owed cloud-rpms spec/scenarios/phase2/w14_patient_messaging_and_communication_spec.rb:15 (-, full, owed; as -)	not run	not run

W15 Reporting (GPRA+)

Journeys: gpra-report-is-run.bpmn.

4 scenarios

Scenario	Test	Analyst	Automated
S-GPR-01.1 `site_manager` Given a year of visits, When I run the GPRA report, Then each measure's numerator and denominator are produced and can be traced to patients.	owed cloud-rpms spec/scenarios/phase2/w15_reporting_gpra_spec.rb:7 (terminal, full, owed; as -)	not run	not run
S-GPR-02.1 `site_manager` Given a GPRA run, When I ask for a measure's patient list, Then the patients not meeting it are listed with what is missing.	owed cloud-rpms spec/scenarios/phase2/w15_reporting_gpra_spec.rb:15 (terminal, full, owed; as -)	not run	not run
S-GPR-03.1 `care_manager` Given a panel of my patients and a GPRA measure some of them have not met, When I open the panel's national measures, Then each patient who has not met the measure is listed against it, and every patient listed lacks the data the measure counts.	owed cloud-rpms spec/scenarios/phase2/w15_reporting_gpra_spec.rb:23 (icare, full, owed; as -)	not run	not run
S-GPR-03.2 `care_manager` Given a patient on the panel who has met every measure, When I open the panel's national measures, Then that patient is not listed as missing any.	owed cloud-rpms spec/scenarios/phase2/w15_reporting_gpra_spec.rb:29 (icare, full, owed; as -)	not run	not run

W16 Credentialing (continued)

Journeys: provider-is-credentialed.bpmn.

1 scenarios

Scenario	Test	Analyst	Automated
S-CRD-03.1 `credentialing_coordinator` Given a provider due for reappointment, When I open their credentials, Then the reappointment date and privileges are shown.	owed cloud-rpms spec/scenarios/phase2/w16_credentialing_continued_spec.rb:7 (terminal, full, owed; as -)	not run	not run

W17 Billing and Revenue Cycle (more programs, third party, clearinghouse)

Journeys: visit-is-billed.bpmn.

1 scenarios

Scenario	Test	Analyst	Automated
S-BIL-04.1 `billing_technician` Given a visit for a patient with private insurance, When the bill is exported to the clearinghouse and the 835 comes back, Then the payment is posted to the bill in A/R.	owed cloud-rpms spec/scenarios/phase2/w17_billing_and_revenue_cycle_more_programs_third_party_clearinghouse_spec.rb:7 (terminal, full, owed; as -)	not run	not run

W18 Admission, Discharge and Transfer (ADT)

Journeys: patient-is-admitted.bpmn.

23 scenarios

Scenario	Test	Analyst	Automated
S-ADT-01.1 `admissions_clerk` Given a registered patient who is not an inpatient, When I admit them with the date and time, type and source of admission, ward, treating specialty, admitting and attending providers and admitting diagnosis, Then PATIENT MOVEMENT (#405) holds an admission movement for the patient with those values, and the patient is a current inpatient on that ward.	planned cloud-rpms spec/features/bprm_adt_spec.rb:21 (bprm, partial, pending; as staging pair)	not run	not run
S-ADT-01.2 `admissions_clerk` Given a required value is missing, When I save the admission, Then it is refused and names the value, and no movement is filed.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:7 (bprm, full, owed; as -)	not run	not run
S-ADT-01.3 `admissions_clerk` Given an admission date and time in the future, When I save the admission, Then it is refused.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:13 (bprm, full, owed; as -)	not run	not run
S-ADT-01.4 `admissions_clerk` Given I hold none of the keys that allow moving a patient (DGZADT, DGZNUR, DGZSUP, DGZSYS), When I open ADT, Then I cannot admit, transfer or discharge.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:19 (bprm, full, owed; as -)	not run	not run
S-ADT-01.5 `admissions_clerk` Given a patient who is already a current inpatient, When I admit them again, Then it is refused and PATIENT MOVEMENT (#405) holds only the one open admission.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:25 (bprm, full, owed; as -)	not run	not run
S-ADT-01.6 `admissions_clerk` Given a ward that is not in WARD LOCATION (#42), or one out of service on the admission date, When I save the admission, Then it is refused and names the ward, and no movement is filed.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:31 (bprm, full, owed; as -)	not run	not run
S-ADT-01.7 `admissions_clerk` Given a patient discharged within the facility's re-admission window, When I admit them, Then the admission is filed and I am warned of the previous discharge with its date.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:37 (bprm, full, owed; as -)	not run	not run
S-ADT-02.1 `nurse` Given a current inpatient, When I transfer them to another ward with the date and time, Then PATIENT MOVEMENT (#405) holds a transfer movement after the admission, and the patient is a current inpatient on the new ward.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:45 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-ADT-02.2 `nurse` Given a current inpatient, When I change their room and bed, Then the bed is theirs and their previous bed is free.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:51 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-ADT-02.3 `nurse` Given a current inpatient, When I change their treating specialty or their attending provider with the date and time, Then PATIENT MOVEMENT (#405) holds a treating-specialty movement with the new specialty and provider.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:57 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-ADT-02.4 `nurse` Given a transfer date and time before the admission, or in the future, When I save the transfer, Then it is refused and no movement is filed.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:63 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-ADT-03.1 `admissions_clerk` Given a current inpatient, When I discharge them with the date and time, discharge type and discharge status, Then PATIENT MOVEMENT (#405) holds a discharge movement tied to the admission, the patient is no longer an inpatient, and their bed is free.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:71 (bprm, full, owed; as -)	not run	not run
S-ADT-03.2 `admissions_clerk` Given a discharge date and time before the admission, or in the future, When I save the discharge, Then it is refused and the patient is still an inpatient.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:77 (bprm, full, owed; as -)	not run	not run
S-ADT-03.3 `admissions_clerk` Given a discharge that transfers the patient to another facility, When I save it without naming the facility, Then it is refused and names the facility.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:83 (bprm, full, owed; as -)	not run	not run
S-ADT-03.4 `admissions_clerk` Given a patient who is not a current inpatient, When I discharge them, Then it is refused and no movement is filed.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:89 (bprm, full, owed; as -)	not run	not run
S-ADT-04.1 `admissions_clerk` Given an admission entered for the wrong patient, When I cancel it and give the reason, Then the admission movement is gone from PATIENT MOVEMENT (#405) and the patient is not an inpatient.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:97 (bprm, full, owed; as -)	not run	not run
S-ADT-04.2 `admissions_clerk` Given a discharge entered in error, When I cancel the discharge, Then the patient is a current inpatient again on the ward they were discharged from.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:103 (bprm, full, owed; as -)	not run	not run
S-ADT-04.3 `admissions_clerk` Given an admission with the wrong admitting diagnosis or provider, When I change the admission's details, Then the admission movement holds the corrected values and no new movement is filed.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:109 (bprm, full, owed; as -)	not run	not run
S-ADT-05.1 `him_technician` Given a discharged patient, When I open an incomplete chart for the stay and record a deficiency against a provider, Then INCOMPLETE CHART (#9009016.1) holds the stay with that provider and deficiency, and the chart is listed as incomplete.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:117 (bprm, full, owed; as -)	not run	not run
S-ADT-05.2 `him_technician` Given an incomplete chart with one deficiency, When I record the date the provider resolved it and the date the chart was completed, Then the chart is no longer listed as incomplete.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:123 (bprm, full, owed; as -)	not run	not run
S-ADT-05.3 `him_technician` Given I hold none of the incomplete-chart keys (DGZICE, DGZPCC, DGZSUP, DGZSYS), When I open ADT, Then I cannot open or change an incomplete chart.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:129 (bprm, full, owed; as -)	not run	not run
S-ADT-06.1 `nurse` Given two patients admitted to a ward and one to another, When I list the current inpatients for the first ward, Then exactly those two are listed, each with their room and bed and attending provider.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:137 (vuecentric, full, owed; as PROFILE,RN)	not run	not run
S-ADT-06.2 `nurse` Given a patient discharged today, When I list today's discharges, Then the patient is listed with the discharge date and type, and is not on the current inpatient list.	owed cloud-rpms spec/scenarios/phase2/w18_admission_discharge_and_transfer_adt_spec.rb:143 (vuecentric, full, owed; as PROFILE,RN)	not run	not run

W19 Benefits and Eligibility

Journeys: coverage-is-recorded.bpmn.

36 scenarios

Scenario	Test	Analyst	Automated
S-BEN-01.1 `benefits_coordinator` Given a patient with Medicare and a private policy on file, When I open their coverage, Then both are listed with the insurer, the policy or beneficiary number and the effective and end dates.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:7 (bprm, full, owed; as -)	not run	not run
S-BEN-01.2 `benefits_coordinator` Given a patient with no coverage on file, When I open their coverage, Then the list is empty and I can add coverage.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:13 (bprm, full, owed; as -)	not run	not run
S-BEN-01.3 `benefits_coordinator` Given coverage on file, When I correct its policy or beneficiary number, Then the file that holds that coverage (MEDICARE ELIGIBLE (#9000003), MEDICAID ELIGIBLE (#9000004) or PRIVATE INSURANCE ELIGIBLE (#9000006)) holds the corrected number and its eligibility dates are unchanged.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:19 (bprm, full, owed; as -)	not run	not run
S-BEN-01.4 `benefits_coordinator` Given coverage on file that no claim has been billed to, When I delete it, Then that coverage file no longer holds it and the patient's other coverage is unchanged.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:25 (bprm, full, owed; as -)	not run	not run
S-BEN-02.1 `benefits_coordinator` Given a patient with no Medicare on file, When I record their Medicare beneficiary identifier, the name on the card, and Part A and Part B with effective dates, Then MEDICARE ELIGIBLE (#9000003) holds the patient with that identifier and one eligibility entry per part with its dates.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:33 (bprm, full, owed; as -)	not run	not run
S-BEN-02.2 `benefits_coordinator` Given a Medicare beneficiary identifier that is not in the identifier's format, When I save, Then it is refused and nothing is filed.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:39 (bprm, full, owed; as -)	not run	not run
S-BEN-02.3 `benefits_coordinator` Given a name on the card that is not `LAST,FIRST MIDDLE`, When I save, Then it is refused and names the format.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:45 (bprm, full, owed; as -)	not run	not run
S-BEN-02.4 `benefits_coordinator` Given a Railroad Retirement beneficiary, When I record their number and parts with effective dates, Then RAILROAD ELIGIBLE (#9000005) holds the patient with those parts and dates.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:51 (bprm, full, owed; as -)	not run	not run
S-BEN-02.5 `benefits_coordinator` Given a patient with Medicare on file, When I record a Part D plan with its insurer, member number and effective date, Then the Part D eligibility is filed with that insurer and listed with the patient's coverage.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:57 (bprm, full, owed; as -)	not run	not run
S-BEN-02.6 `benefits_coordinator` Given a Medicare part recorded in error, When I remove that eligibility entry, Then MEDICARE ELIGIBLE (#9000003) no longer holds it and the other parts are unchanged.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:63 (bprm, full, owed; as -)	not run	not run
S-BEN-03.1 `benefits_coordinator` Given a patient with no Medicaid on file, When I record their Medicaid number, the name on the card, the state's plan and an eligibility period, Then MEDICAID ELIGIBLE (#9000004) holds the patient with that number, plan and period.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:71 (bprm, full, owed; as -)	not run	not run
S-BEN-03.2 `benefits_coordinator` Given a plan that requires a rate code, When I save without one, Then it is refused and names the rate code.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:77 (bprm, full, owed; as -)	not run	not run
S-BEN-03.3 `benefits_coordinator` Given a Medicaid eligibility period that has ended, When I add the new period, Then both periods are on file and only the new one covers today.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:83 (bprm, full, owed; as -)	not run	not run
S-BEN-04.1 `benefits_coordinator` Given a patient who holds a policy, When I record the insurer, policy number, coverage type and effective date with the patient as holder, Then POLICY HOLDER holds the policy and PRIVATE INSURANCE ELIGIBLE (#9000006) holds the patient as a member of it.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:91 (bprm, full, owed; as -)	not run	not run
S-BEN-04.2 `benefits_coordinator` Given a policy held by the patient's parent, When I add the patient as a member with their relationship to the holder, Then PRIVATE INSURANCE ELIGIBLE (#9000006) holds the patient under that policy with that relationship.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:97 (bprm, full, owed; as -)	not run	not run
S-BEN-04.3 `benefits_coordinator` Given a member added to a policy in error, When I remove the member, Then the policy and its other members are unchanged.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:103 (bprm, full, owed; as -)	not run	not run
S-BEN-04.4 `benefits_coordinator` Given coverage that a claim has already been billed to, When I ask to delete the coverage, Then I am warned that claims use it before anything is deleted.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:109 (bprm, full, owed; as -)	not run	not run
S-BEN-04.5 `benefits_coordinator` Given a new policy holder with no relationship to the insured, name as on the policy, policy number, effective date, sex, date of birth or address, When I save, Then it is refused, names the field, and nothing is filed.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:115 (bprm, full, owed; as -)	not run	not run
S-BEN-05.1 `benefits_coordinator` Given a patient with Medicare, When I record the survey with the date it was given, the answers and the signature date, Then MSP PATIENT holds a survey for that date with those answers.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:123 (bprm, full, owed; as -)	not run	not run
S-BEN-05.2 `benefits_coordinator` Given a survey already on file for a date, When I record another for the same date, Then it is refused.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:129 (bprm, full, owed; as -)	not run	not run
S-BEN-05.3 `benefits_coordinator` Given a signature date before the date the survey was given, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:135 (bprm, full, owed; as -)	not run	not run
S-BEN-06.1 `benefits_coordinator` Given a patient with Medicare and a private policy, When I set the private policy first and Medicare second for medical visits from today, Then the patient's sequence for that category and date is filed in that order.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:143 (bprm, full, owed; as -)	not run	not run
S-BEN-06.2 `benefits_coordinator` Given a sequence on file, When I remove it, Then the patient has no sequence for that category and their coverage is unchanged.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:149 (bprm, full, owed; as -)	not run	not run
S-BEN-07.1 `benefits_coordinator` Given a patient with a private policy, When I record an authorization with the encounter date, insurer, authorization number and date, and the person who authorized it, Then PRIOR AUTHORIZATIONS (#9000046) holds it for the patient with that contact.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:157 (bprm, full, owed; as -)	not run	not run
S-BEN-07.2 `benefits_coordinator` Given an authorization on file, When I add additional authorized days, Then the authorization holds them and its original days are unchanged.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:163 (bprm, full, owed; as -)	not run	not run
S-BEN-07.3 `benefits_coordinator` Given an authorized amount of zero, When I save, Then it is refused.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:169 (bprm, full, owed; as -)	not run	not run
S-BEN-07.4 `benefits_coordinator` Given no encounter date or no authorization type, When I save the authorization, Then it is refused and nothing is filed.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:175 (bprm, full, owed; as -)	not run	not run
S-BEN-08.1 `benefits_coordinator` Given a patient injured at work, When I record the date of injury, the insurer and the claim number, Then WORKMAN'S COMPENSATION (#9000042) holds the claim for the patient under that date of injury.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:183 (bprm, full, owed; as -)	not run	not run
S-BEN-08.2 `benefits_coordinator` Given a patient injured in an accident where another party is liable, When I record the date of injury and the responsible party, Then THIRD PARTY LIABILITY (#9000041) holds it for the patient under that date of injury.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:189 (bprm, full, owed; as -)	not run	not run
S-BEN-09.1 `benefits_coordinator` Given a minor patient, When I record a parent as guarantor with an effective date, Then GUARANTOR (#9000043) holds the parent for the patient from that date.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:197 (bprm, full, owed; as -)	not run	not run
S-BEN-09.2 `benefits_coordinator` Given a guarantor on file, When I end their responsibility and record a new guarantor from the next day, Then both are on file and only the new one is responsible today.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:203 (bprm, full, owed; as -)	not run	not run
S-BEN-10.1 `benefits_coordinator` Given an uninsured patient referred to me, When I open a case with the date assigned, the reason and myself as the coordinator, Then BENEFIT COORDINATOR CASES (#9000044) holds an open case for the patient assigned to me.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:211 (bprm, full, owed; as -)	not run	not run
S-BEN-10.2 `benefits_coordinator` Given an open case, When I record an application with its type, the date it was obtained and the date it was submitted, Then PATIENT APPLICATIONS (#9000045) holds the application for the patient with those dates.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:217 (bprm, full, owed; as -)	not run	not run
S-BEN-10.3 `benefits_coordinator` Given an open case, When I complete it with a date before the date it was assigned, Then it is refused.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:223 (bprm, full, owed; as -)	not run	not run
S-BEN-10.4 `benefits_coordinator` Given a completed case and a user without the re-open key (AGZCREOPN), When they try to re-open it, Then it is refused and the case stays completed.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:229 (bprm, full, owed; as -)	not run	not run
S-BEN-10.5 `benefits_coordinator` Given no date assigned, no coordinator assigned or no reason, When I open the case, Then it is refused and nothing is filed.	owed cloud-rpms spec/scenarios/phase2/w19_benefits_and_eligibility_spec.rb:235 (bprm, full, owed; as -)	not run	not run

W20 Population and Care Management (iCare)

Journeys: population-is-managed.bpmn.

15 scenarios

Scenario	Test	Analyst	Automated
S-POP-01.1 `care_manager` Given appointments today with two providers and with a third, When I create a panel of today's scheduled patients for the first two providers, Then the panel lists exactly the patients booked with those two today, and ICARE USER (#90505) holds the panel under me with those patients.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:7 (icare, full, owed; as -)	not run	not run
S-POP-01.2 `care_manager` Given that panel and an appointment booked with one of the two providers after it was created, When I repopulate the panel, Then the new patient is on it.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:13 (icare, full, owed; as -)	not run	not run
S-POP-02.1 `care_manager` Given patients whose latest BMI is 30 or more and patients whose latest BMI is under 30, When I create a panel of patients with a latest BMI of 30 or more, Then the panel lists exactly the first group.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:21 (icare, full, owed; as -)	not run	not run
S-POP-03.1 `care_manager` Given a panel I own, When I share it with a second iCare user, Then the panel's shares (node 30 under it in ICARE USER #90505) hold that user, and the panel is in their panel list with the same patients.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:29 (icare, full, owed; as -)	not run	not run
S-POP-03.2 `care_manager` Given a panel shared with a user for reading only, When that user tries to change its patients, Then it is refused and the panel is unchanged.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:35 (icare, full, owed; as -)	not run	not run
S-POP-04.1 `care_manager` Given female and male patients of several ages, When I create a panel of female patients aged 18 to 50, Then the panel lists exactly the women aged 18 to 50.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:43 (icare, full, owed; as -)	not run	not run
S-POP-04.2 `care_manager` Given that panel, When I open its national measures, Then each measure shows how many of the panel's patients meet it and how many do not.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:49 (icare, full, owed; as -)	not run	not run
S-POP-05.1 `care_manager` Given a patient on my panel with an emergency room visit within my flag time frame (one month by default), When I open the flag list, Then the visit is listed as a flag for that patient.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:57 (icare, full, owed; as -)	not run	not run
S-POP-05.2 `care_manager` Given that flag, When I mark it as reviewed, Then it is no longer listed as new.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:63 (icare, full, owed; as -)	not run	not run
S-POP-06.1 `care_manager` Given a patient with a queued care management event, When I track it, Then it moves from the queued events to the tracked events for that patient.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:71 (icare, full, owed; as -)	not run	not run
S-POP-06.2 `care_manager` Given a tracked event, When I record its follow-up, Then the event shows the follow-up and is no longer due.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:77 (icare, full, owed; as -)	not run	not run
S-POP-07.1 `care_manager` Given a visit with a diagnosis on the mandatory community alert list within the alert time frame (30 days by default), When I open community alerts, Then ICARE COMMUNITY ALERTS (#90507.6) holds an alert for that disease and date, and the main view lists it.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:85 (icare, full, owed; as -)	not run	not run
S-POP-07.2 `care_manager` Given a user without the Community Alerts Detail key, When they open community alerts, Then they see the alert counts and not the alert's details.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:91 (icare, full, owed; as -)	not run	not run
S-POP-08.1 `care_manager` Given a patient whose visits and labs meet a condition's criteria, When I open the patient's diagnosis tags, Then the condition is listed as Proposed.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:99 (icare, full, owed; as -)	not run	not run
S-POP-08.2 `care_manager` Given a proposed tag, When I accept it, Then the tag is Accepted, and a panel of patients with that tag accepted includes the patient.	owed cloud-rpms spec/scenarios/phase2/w20_population_and_care_management_icare_spec.rb:105 (icare, full, owed; as -)	not run	not run

W21 Behavioral Health Data Segregation (42 CFR Part 2)

Journeys: bh-note-is-protected.bpmn.

12 scenarios

Scenario	Test	Analyst	Automated
S-BH-01.1 `bh_provider` Given a visit in context, a behavioral health title whose VIEW rule in USR AUTHORIZATION/SUBSCRIPTION (#8930.1) names only behavioral health user classes, and my membership in one of them (USR CLASS MEMBERSHIP #8930.3), When I write a note under that title and sign it with my electronic signature, Then TIU DOCUMENT (#8925) holds the note, completed, under that title, linked to the visit.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:7 (vuecentric, full, owed; as -)	not run	not run
S-BH-01.2 `bh_provider` Given my signed note, When I open it again, Then I see its text.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:13 (vuecentric, full, owed; as -)	not run	not run
S-BH-01.3 `bh_provider` Given a user who is in none of the title's user classes, When they look for a title to write under, Then the behavioral health titles are not offered to them, if the site gives the titles an ENTRY rule as well as a VIEW rule.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:19 (vuecentric, full, owed; as -)	not run	not run
S-BH-02.1 `provider` Given a patient with a signed behavioral health note, and my user in none of the title's user classes, When I open the patient's notes, Then the note is listed with its title, date and author.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:27 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-BH-02.2 `provider` Given the same note, When I open it, Then its text is not shown, and I am told I may not view it.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:33 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-BH-02.3 `provider` Given the same note, When I print the patient's notes, Then its text is not printed, because the title also has a PRINT RECORD rule (USR ACTION #8930.8 holds VIEW and PRINT RECORD as separate actions).	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:39 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-BH-03.1 `provider` Given a behavioral health note I may not view, When I break the glass and give a reason, Then I see the note's text, and the access is recorded with my user, the patient, the note, the date and time, and my reason.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:47 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-BH-03.2 `provider` Given a behavioral health note I may not view, When I start to break the glass and cancel, Then the text stays hidden and nothing is recorded.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:53 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-BH-03.3 `provider` Given a patient whose record is marked sensitive in DG SECURITY LOG (#38.1), and my user without the DG SENSITIVITY key, When I select the patient and confirm that I have a need to know, Then the chart opens, DG SECURITY LOG holds my access in its access multiple (#38.11) with the date and time, my user and the option, and the RESTRICTED PATIENT RECORD ACCESSED bulletin goes to the mail group MAS PARAMETERS (#43) names.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:59 (vuecentric, full, owed; as PROFILE,MD)	not run	not run
S-BH-04.1 `him_technician` Given accesses to a sensitive patient's record by several users, When I list the users who accessed the record over a date range, Then each access is listed with the user, the date and time and the option used, as DG SECURITY LOG (#38.1) holds them.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:67 (bprm, full, owed; as -)	not run	not run
S-BH-04.2 `him_technician` Given my user without the DG SECURITY OFFICER key, When I ask for the list, Then I am refused, and told I do not have the privileges to display user access.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:73 (bprm, full, owed; as -)	not run	not run
S-BH-04.3 `him_technician` Given a break-the-glass on a behavioral health note (S-BH-03.1), When I list the accesses to the patient's record, Then the break-the-glass is listed with the user, the note, the date and time, and the reason given.	owed cloud-rpms spec/scenarios/phase2/w21_behavioral_health_data_segregation_42_cfr_part_2_spec.rb:79 (bprm, full, owed; as -)	not run	not run

Tabs with no story

The chart tabs this branch's capture shows (12) that no story's step lands on. A tab a user works on is a step someone performs, so each needs at least one story.

None on this capture.

Checks not tied to a scenario

Tests that exist but prove no scenario yet: each is either a story waiting to be written, or a technical check that stays one.

cloud-rpms spec/features/bprm_spec.rb:28: BPRM web a clerk logs in with their RPMS access/verify pair
cloud-rpms spec/features/bprm_spec.rb:37: BPRM web the Reports area renders after login
cloud-rpms spec/features/cia_broker_rpc_spec.rb:71: RPC broker :9100 through rpms-rpc (CiaClient) signs on over the wire with the stack's staging pair
cloud-rpms spec/features/cia_broker_rpc_spec.rb:78: RPC broker :9100 through rpms-rpc (CiaClient) answers BEHOVM2 VUNITS for a known vital (rpms-ops#510 fault fixed)
cloud-rpms spec/features/cia_broker_rpc_spec.rb:85: RPC broker :9100 through rpms-rpc (CiaClient) answers BEHOVM2 VUNITS for an unknown vital with an empty result, not a dropped session
cloud-rpms spec/features/cia_broker_rpc_spec.rb:99: RPC broker :9100 through rpms-rpc (CiaClient) survives a faulting RPC: the listener serves a fresh session again within 90s (rpms-ops#477)
cloud-rpms spec/features/roll_and_scroll_spec.rb:19: RPMS roll-and-scroll a user signs on at the terminal and reaches the menu system
cloud-rpms spec/features/vuecentric/provider_spec.rb:86: VueCentric: the provider Reports > Health Summary > Adult Regular shows the patient's summary and offers to print it