One Patient, Two Workflows
Follow one patient's source records into a clinician-reviewed note, a follow-up workflow, and a confirmed scheduling outcome.
A new application starts with useful context when patient identity, source history, and reviewed observations carry forward from earlier work. Follow Alex Morgan from a prescription through a clinician-reviewed note to a completed follow-up task.
Use the tabs to follow the patient story, inspect source evidence, and review application ownership and reuse.
How the Record Grows
Prescription, April 6. An EHR contributes an active blood-pressure prescription. Its source and observation time remain attached to the record. A prescription establishes what was prescribed; it does not establish what Alex took.
Patient report, April 9. Alex says, "I have skipped a few doses. I have also felt dizzy. Afternoon calls work best for me." Reported use, symptoms, and contact preference join the same history. They remain distinguishable from the prescription.
Measurements, April 10. An authorized monitoring feed contributes two blood-pressure observations with dates and units. The clinician can inspect them alongside the prescription and conversation. The record does not infer that the medication caused the dizziness.
Reviewed note, April 10. The clinician reviews the evidence and approves a care-team check-in. Scribe owns the note and review workflow. The configured publication integration contributes the approved instruction as shared context for the next application. No medication change is authorized in this case.
Follow-up request, April 10. The follow-up application uses the patient reference, reviewed instruction, and afternoon contact preference. It checks current scheduling availability; Alex selects April 11 at 14:30 UTC. The request is submitted and the task remains pending.
Confirmed result, April 10. The scheduling system confirms the appointment. A read-back returns the same patient, appointment, and time. The application closes its task, and the shared patient view incorporates the confirmed result.
The completed work is a confirmed booking. Attendance, patient benefit, and clinical outcomes would enter the history as separate observations.
Follow the Source References
Every record in this case refers to example-patient-001. The evidence file retains source text, example record identifiers, observation time, receipt time, and the time each observation becomes available in the shared view.
EHR prescription
example-rx-001
A prescription was recorded for Alex
Patient conversation
example-conversation-001
Alex reported missed doses and dizziness, and requested afternoon calls
Authorized measurements
example-readings-001
Two observations with measurement times and units
Clinician-reviewed note
example-note-001
The reviewed instruction authorizes a care-team check-in
Follow-up application
example-task-001
The selected slot and attempted scheduling action
Scheduling confirmation
example-appointment-001
The source confirmed the booking and a read-back matched it
Receipt, Projection, and Source Confirmation
At the follow-up step, the request event has been received, its shared-view projection is still pending, and the scheduling system has not confirmed the action.
Request event received
April 10, 14:01:01 UTC
The request is recorded; the application still awaits confirmation
Request visible in shared view
April 10, 14:03:00 UTC
A reader can see the request; the booking is still a separate transaction
Booking confirmed by source
April 10, 14:04:00 UTC
The scheduling result, supported by read-back, allows the task to complete
Confirmed result in shared view
April 10, 14:05:00 UTC
A later application can read the confirmed outcome
If the source response is missing or ambiguous, the task stays unresolved while its owner reconciles the scheduling record. An event receipt, approved note, or agent statement cannot substitute for source confirmation.
The World Model explains provenance and projection. Verify an Integration Action explains how to collect external-action evidence in a provisioned test.
What Each Part Owns
Data platform
Retain source evidence, connect the patient references, and produce the shared patient view
Events
Communicate accepted changes to consumers; receipt and consumer completion remain separate signals
Scribe
Own the note draft and clinician review
Configured publication integration
Publish the reviewed observation and instruction with the required patient and source references
Follow-up application
Own the task, channel checks, action permissions, scheduling request, and recovery
Scheduling system
Confirm the authoritative appointment state
What the Second Workflow Reuses
The follow-up application reuses the patient reference, connected prescription and measurement history, reviewed instruction, and contact preference. It does not need to ask Alex to reconstruct that history in a new conversation.
The application still needs permission to perform its specific action, a current availability lookup, and its own task and recovery state. Shared read access does not grant scheduling write access. Source access and patient visibility remain scoped to the authorized workspace and workflow.
For an evaluation, record which connectors, identity mappings, data definitions, and functions were reused; which action or channel configuration was newly required; and the effort to reach the second accepted outcome. Compare equivalent work and keep access lead time separate from implementation effort. Use the Technical Evaluation Packet to record the result.
Download the Case
note-to-follow-up, version 1.Continue Your Review
World Model - identity, retained observations, and serving views.
Shared Context and Applications - the three-part ownership map.
Connect Another Workflow - participation contract, recovery tests, and a reuse worksheet.
How It Works - workflow execution and external confirmation.
Technical Evaluation Packet - acceptance criteria and a decision record.
Scribe: Capture to Note - the note workflow's implementation contract.
Last updated
Was this helpful?