synthetic-hl7-feed
hl7-event-feed
interface engine and workflow owner review before live HL7 event routing
Request signals
fixture-hl7-event-feed-v1
hl7-v2-event-synthetic-v1 fixture from synthetic-hl7-feed
01eventType: Synthetic ADT, ORM, or ORU event category.
02patientReference: Synthetic patient pointer without production identifiers.
03timestamp: Original event timestamp preserved as the orchestration clock.
04facility: Synthetic facility code and care setting.
05orderingContext: Synthetic order/result metadata for workflow routing.
Expected signals produced after contract normalization.
- eventType
- patientReference
- timestamp
- facility
- orderingContext
Signals that block fixture acceptance when absent.
- eventType
- patientReference
- timestamp
Unsafe connector behavior that must stay blocked.
- silent event drop
- timestamp overwrite
- unreviewed clinical trigger
Fixture payload present
Every non-synthetic integration contract must have a synthetic request and expected-response fixture.
Synthetic-only fixture
Integration fixture requests must be explicitly synthetic-only until live connector approval.
Contract binding
Fixture and request payload must bind to the same integration contract slug.
No production identifiers
Fixture payload must not include obvious SSN, MRN, email, or phone identifiers.
Required signals covered
Fixture must cover every required signal declared by the integration contract.
Safeguards mapped
Fixture text must map all declared safeguards into guardrails, trace, review, or prohibited-action controls.
Trace complete
Expected response must include at least four deterministic trace steps.
Live review required
Fixture must require human review before live connector promotion.
Prohibited actions
Expected response must define prohibited actions for unsafe connector behavior.
Diff fingerprint
Fixture diff fingerprint must change when expected request or response fields change.