Guided episode · Maya Sen is entirely fictional
Rivermark Demonstration Networkscene-0Seed417Minimum payloads and active routes
map at rest
The map at rest
This is a logical map of capabilities, not a physical network diagram.
No transaction has started; every component is available for inspection.
A static diagram can falsely imply one server, one database, or one mandatory deployment.
- Registration message enters the exchange: community-app to iol, not invoked in this transaction.
- Clinic request or artifact enters the exchange: clinic-ehr to iol, not invoked in this transaction.
- Hospital requests a permitted shared summary: hospital-ehr to iol, not invoked in this transaction.
- Laboratory receives an order or returns a result: laboratory to iol, not invoked in this transaction.
- Pharmacy submits a minimum supply event: pharmacy to iol, not invoked in this transaction.
- The sending system credential is checked: iol to authentication, not invoked in this transaction.
- Worker, organization, location and service are related: iol to interlinking, not invoked in this transaction.
- Identity evidence is evaluated: iol to entity-matching, not invoked in this transaction.
- Purpose and disclosure policy are evaluated: iol to policy, not invoked in this transaction.
- Local and enterprise identity links are queried: iol to client-registry, not invoked in this transaction.
- Canonical facility status and endpoint are queried: iol to facility-registry, not invoked in this transaction.
- Canonical worker role and status are queried: iol to health-worker-registry, not invoked in this transaction.
- A versioned semantic mapping is requested: iol to terminology-service, not invoked in this transaction.
- A fictional product identity is resolved: iol to product-catalogue, not invoked in this transaction.
- A redacted operation event and derivation evidence are recorded: iol to audit-evidence, not invoked in this transaction.
- A permitted normalized clinical subset is read or written: iol to shared-health-record, not invoked in this transaction.
- A periodic minimized aggregate is exported: iol to hmis, not invoked in this transaction.
- A minimum supply event changes represented stock: iol to lmis, not invoked in this transaction.
- A separate fictional eligibility or claim state is exchanged: iol to finance-insurance, not invoked in this transaction.
Active station spine
20 capabilities are deliberately marked “Not invoked in this transaction.” The active route resets whenever the authored transaction changes.
Accessible transcript
The whole journey, without motion
Every chapter and technical operation appears in document order before the simulation hydrates.
- 00
The map at rest
This is a logical map of capabilities, not a physical network diagram.
Technical operation
No transaction has started; every component is available for inspection.
- 01
A local identity arrives
Maya arrives at Lumenbank Clinic, which knows a local identifier and a small local record.
Technical operation
The Clinic EHR shows immutable source artifact SYN-ART-REG-00417-V1 before exchange.
- 02
The message receives an envelope
The local request gets operational identifiers without duplicating its payload.
Technical operation
The IOL creates illustrative demo-exchange-envelope-v1 with a payload reference and deterministic attempt metadata.
- 03
Trust forks and joins
Identity, status, relationships, and policy are checked separately before anything clinical is disclosed.
Technical operation
The IOL fans out simulated authentication, facility, worker, interlinking, and policy checks, then joins their outcomes.
- 04
Identity is resolved
Two retained local identifiers point to one synthetic enterprise identity.
Technical operation
The Client Registry and entity-matching capability return linkage evidence for SYN-CR-000184.
- 05
A limited history returns
The clinic receives only the small shared subset that exists and is permitted.
Technical operation
The IOL queries the SHR by enterprise identity; clinical content and acknowledgement remain separate artifacts.
- 06
A local test order needs portable meaning
The local order changes shape and receives a governed semantic derivative while its original coding stays visible.
Technical operation
Mediator SYN-MEDIATOR-1.0.0 creates demo-canonical-v1; ConceptMap SYN-CM-LUMENBANK-LAB version 1.2.0 maps LUM-HB to LOINC 718-7.
- 07
The laboratory answers
The laboratory asserts a synthetic result; the exchange stores a traceable normalized version without overwriting the source.
Technical operation
The IOL validates context and terminology, routes to the clinic and SHR, then records separate audit and provenance evidence.
- 08
Product identity and stock are different questions
A product catalogue defines the fictional pack; the LMIS alone changes stock.
Technical operation
A distinct dispense-and-supply transaction resolves SYN-PC-IRON-001 and sends only a minimum supply event to the LMIS.
- 09
Payment is a separate domain
A fictional coverage service answers a finance question without becoming a clinical record.
Technical operation
A distinct eligibility-and-claim transaction produces only eligible-for-demo and claim-received toy states.
- 10
The population view is derived later
At a later period boundary, person identifiers peel away and one aggregate contribution moves asynchronously.
Technical operation
A governed aggregation step derives an identifier-free HMIS count with a small-cell warning; it cannot edit the SHR.
- 11
The record crosses town
A later authorized hospital query reveals distinct, permitted views—not one enormous database. The record did not become one record everywhere. It became traceable, interpretable, and available where the rules allowed it.
Technical operation
Eastbridge repeats trust and identity checks, then retrieves a limited SHR summary while LMIS, HMIS, and FIS retain separate domain state.
Journey ready. Nothing is playing.