synthetic-fhir-server
fhir-clinical-record-intake
integration architect and clinical governance review before live FHIR connection
Request signals
fixture-fhir-clinical-record-intake-v1
fhir-r4-synthetic-v1 fixture from synthetic-fhir-server
01patient: Synthetic Patient resource with demographic band only.
02encounter: Synthetic Encounter resource with class, period, and care setting.
03observation: Synthetic Observation resources for vitals and lab-like signals.
04condition: Synthetic Condition resources with coded problem context.
05medication: Synthetic MedicationRequest resources with active/reconciled status.
06carePlan: Synthetic CarePlan resource with reviewable care coordination goals.
Expected signals produced after contract normalization.
- patient
- encounter
- observation
- condition
- medication
- carePlan
Signals that block fixture acceptance when absent.
- patient
- encounter
- source resource trace
Unsafe connector behavior that must stay blocked.
- production data ingestion
- silent mutation
- clinical action without review
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.