Build a Clinical Interoperability Sandbox Communication Dispatch Monitor
Track message transit latency and schema conformance for simulated FHIR care-team communication events. Detect malformed routing headers and maintain verifiable delivery audit traces.
What you are building
The core problem, expected build, and operating context for this challenge.
Track message transit latency and schema conformance for simulated FHIR care-team communication events. Detect malformed routing headers and maintain verifiable delivery audit traces.
Interoperability Test Engineer
Ingest simulated FHIR R5 Communication and MessageHeader event streams via HTTP webhook.
Validate resource structure and sender/recipient endpoint compliance against FHIR schemas.
Calculate end-to-end simulated dispatch transit latencies and track dropped messages.
Instrument telemetry traces and generate automated conformance scorecards for integration teams.
Real-time message traffic monitor displaying payload schema validity, transit latency gauges, and failed route alerts.
Generate synthetic FHIR R5 event streams using local Python mock scripts based on HL7 documentation. Starter examples below are synthetic. They are not downloaded records.
HL7 FHIR overview Utilize FHIR Foundation MessageHeader and Conformance StructureDefinition rules to score inbound message syntax.
langfuse, fastapi, pydantic. langfuse monitors message delivery latencies, schema evaluation runs, and error rates across test suites. Local API or hosted model for automated log classification and error narrative generation.
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
Validates incoming simulated FHIR message payloads against required FHIR R5 header fields.
Computes simulated delivery duration and flags latencies exceeding pre-configured thresholds.
Logs telemetry spans to Langfuse for each dispatch transaction.
Exports a downloadable JSON audit scorecard detailing schema violations.
```json [ { "input": { "batch_id": "DISP-01", "messages": [ { "id": "M1", "resourceType": "MessageHeader", "eventCoding": { "system": "http://example.org/events", "code": "care-team-alert" }, "source": { "endpoint": "urn:source:lab" }, "destination": [ { "endpoint": "urn:dest:ward" } ] } ] }, "expected_output": { "batch_id": "DISP-01", "total_processed": 1, "valid_headers": 1, "schema_errors": 0, "audit_status": "conforming" } }, { "input": { "batch_id": "DISP-02", "messages": [ { "id": "M2", "resourceType": "MessageHeader", "source": { "endpoint": "urn:source:lab" } } ] }, "expected_output": { "batch_id": "DISP-02", "total_processed": 1, "valid_headers": 0, "schema_errors": 1, "audit_status": "non_conforming" } } ] ```
Software testing sandbox tool; processes synthetic telemetry; no protected clinical data or real patient care delivery. Use mock external writes. Require human review before any real deployment.
Participation guide
Software testing sandbox tool; processes synthetic telemetry; no protected clinical data or real patient care delivery. Use mock external writes and human review.
How work is evaluated
Validates incoming simulated FHIR message payloads against required FHIR R5 header fields. Computes simulated delivery duration and flags latencies exceeding pre-configured thresholds. Logs telemetry spans to Langfuse for each dispatch transaction. Exports a downloadable JSON audit scorecard detailing schema violations.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Ingest simulated FHIR R5 Communication and MessageHeader event streams via HTTP webhook. Validate resource structure and sender/recipient endpoint compliance against FHIR schemas. Calculate end-to-end simulated dispatch transit latencies and track dropped messages. Instrument telemetry traces and generate automated conformance scorecards for integration teams.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Validates incoming simulated FHIR message payloads against required FHIR R5 header fields. Computes simulated delivery duration and flags latencies exceeding pre-configured thresholds. Logs telemetry spans to Langfuse for each dispatch transaction. Exports a downloadable JSON audit scorecard detailing schema violations.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Real-time message traffic monitor displaying payload schema validity, transit latency gauges, and failed route alerts.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Software testing sandbox tool; processes synthetic telemetry; no protected clinical data or real patient care delivery.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Ingest simulated FHIR R5 Communication and MessageHeader event streams via HTTP webhook.
Validate resource structure and sender/recipient endpoint compliance against FHIR schemas.
Calculate end-to-end simulated dispatch transit latencies and track dropped messages.
Instrument telemetry traces and generate automated conformance scorecards for integration teams.
Reference links and supporting material
Generate synthetic FHIR R5 event streams using local Python mock scripts based on HL7 documentation. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
Langfuse
Open-source LLM observability and evals.
Evaluated output
No output checks are configured.
- Ingest simulated FHIR R5 Communication and MessageHeader event streams via HTTP webhook. Validate resource...
- Validates incoming simulated FHIR message payloads against required FHIR R5 header fields. Computes simulat...
- Real-time message traffic monitor displaying payload schema validity, transit latency gauges, and failed ro...
- 2 public reference cases
- 2 configured tools
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- Langfuse · Optional
- Langfuse · Optional
Evaluation contract
- Complete workflow · Weight 40
- Correctness and evidence · Weight 30
- Review interface · Weight 20
- Safe execution · Weight 10
Reference cases
- 2 public reference cases
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.