Build a FHIR StructureDefinition Molecular Profile Verifier
Validate custom genomics research observation instances against FHIR StructureDefinition rules. Detect schema deviations, cardinality errors, and missing mandatory molecular codes.
What you are building
The core problem, expected build, and operating context for this challenge.
Validate custom genomics research observation instances against FHIR StructureDefinition rules. Detect schema deviations, cardinality errors, and missing mandatory molecular codes.
Clinical Interoperability Engineer
Ingest FHIR R5 StructureDefinition profiles specifying required molecular observation attributes.
Parse incoming research observation JSON objects to check datatype conformity and cardinality.
Inspect terminology bindings to verify standard code systems for gene symbols and sequence types.
Generate conformance reports highlighting valid elements and actionable validation errors.
Developer terminal CLI and web-based diff viewer comparing observed resources against StructureDefinition.
Use official HL7 FHIR R5 core StructureDefinition JSON schemas downloaded from the published standard. Starter examples below are synthetic. They are not downloaded records.
HL7 FHIR overview Directly implements StructureDefinition constraints, cardinality checks, and terminology bindings from FHIR specification Section 2.1.15.3.1.
pydantic-ai, fastapi, pytest. Provides deterministic type validation and model enforcement matching FHIR StructureDefinition constraints. Local open LLM or standard hosted API used only for generating human-readable remediations.
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 JSON payloads against FHIR R5 Observation StructureDefinition cardinality rules.
Flags missing mandatory fields such as 'status', 'code', and 'resourceType'.
Produces a structured conformance score with explicit JSON-pointer error locations.
```json [ { "input": { "resourceType": "Observation", "status": "final", "code": { "coding": [ { "system": "http://loinc.org", "code": "48018-6", "display": "Gene studied [Identifier]" } ] }, "valueString": "BRCA1" }, "expected_output": { "conforms": true, "schema": "FHIR-R5-Observation", "missing_elements": [], "cardinality_violations": [], "conformance_score": 1 } }, { "input": { "resourceType": "Observation", "valueString": "BRCA1" }, "expected_output": { "conforms": false, "schema": "FHIR-R5-Observation", "missing_elements": [ "status", "code" ], "cardinality_violations": [ "Observation.status: minimum cardinality 1, found 0" ], "conformance_score": 0.33 } } ] ```
Technical schema validation of synthetic research payloads; strictly excludes clinical health records. Use mock external writes. Require human review before any real deployment.
Participation guide
Technical schema validation of synthetic research payloads; strictly excludes clinical health records. Use mock external writes and human review.
How work is evaluated
Validates JSON payloads against FHIR R5 Observation StructureDefinition cardinality rules. Flags missing mandatory fields such as 'status', 'code', and 'resourceType'. Produces a structured conformance score with explicit JSON-pointer error locations.
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 FHIR R5 StructureDefinition profiles specifying required molecular observation attributes. Parse incoming research observation JSON objects to check datatype conformity and cardinality. Inspect terminology bindings to verify standard code systems for gene symbols and sequence types. Generate conformance reports highlighting valid elements and actionable validation errors.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Validates JSON payloads against FHIR R5 Observation StructureDefinition cardinality rules. Flags missing mandatory fields such as 'status', 'code', and 'resourceType'. Produces a structured conformance score with explicit JSON-pointer error locations.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Developer terminal CLI and web-based diff viewer comparing observed resources against StructureDefinition.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Technical schema validation of synthetic research payloads; strictly excludes clinical health records.
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 FHIR R5 StructureDefinition profiles specifying required molecular observation attributes.
Parse incoming research observation JSON objects to check datatype conformity and cardinality.
Inspect terminology bindings to verify standard code systems for gene symbols and sequence types.
Generate conformance reports highlighting valid elements and actionable validation errors.
Reference links and supporting material
Use official HL7 FHIR R5 core StructureDefinition JSON schemas downloaded from the published standard. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
Pydantic AI
Typed Python agent framework.
Evaluated output
No output checks are configured.
- Ingest FHIR R5 StructureDefinition profiles specifying required molecular observation attributes. Parse inc...
- Validates JSON payloads against FHIR R5 Observation StructureDefinition cardinality rules. Flags missing ma...
- Developer terminal CLI and web-based diff viewer comparing observed resources against StructureDefinition.
- 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
- Pydantic AI · Optional
- Pydantic AI · 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.