The receiving half of the interface. POST HL7v2, C-CDA, or a Redox message into the sandbox and it lands as FHIR — the inverse of the living data feed that emits those same formats. Plus topic-based FHIR Subscriptions for standards-shaped push.
POST an HL7v2 message and get a real ACK back, shaped per vendor — MSH-3 sending application and accept policy follow the deployment you addressed. ADT admit and register messages upsert a Patient and open an Encounter; discharge closes it. ORU^R01 results become one Observation per value OBX plus a DiagnosticReport that links them. ORM^O01 orders become a ServiceRequest. Anything else NAKs with MSA|AR, which is itself a case worth testing.
POST a C-CDA R2.1 XML document and receive a FHIR OperationOutcome as the acknowledgement, with the real diagnostics when a write is rejected rather than a generic failure. Hostile input — entity expansion, external DTDs, non-finite numeric lab values — returns a clean 400 instead of a 500.
Register the sandbox as a Redox destination and deliver to it with Redox-native auth, including the verification-token header and the empty-body verification probe. Literal references are resolved against the receiving partition and demoted to identifier or display when unresolvable, so a delivery cannot dangle a reference the server would reject.
Topic-based FHIR Subscriptions deliver notifications on matching events, so you can test push-shaped integrations rather than only poll-shaped ones. Inbound writes and subscriptions are Pro features; see pricing.