Skip to main content
Challenge

Build a FHIR StructureDefinition Conformance and Sequence Evidence Auditor

Inspect research observation payloads against FHIR R5 StructureDefinition rules. Validate sequence annotation properties and generate conformance scorecards for multi-center registries.

Data ScienceHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Inspect research observation payloads against FHIR R5 StructureDefinition rules. Validate sequence annotation properties and generate conformance scorecards for multi-center registries.

Health Informatics Specialist

Ingest FHIR JSON resources representing molecular and genomic observations.

Validate required element cardinality and terminology bindings against FHIR R5 specifications.

Detect missing data types, invalid code systems, or malformed narrative sections.

Produce an interoperability audit report with remediation instructions.

Interactive browser portal presenting conformance issues with interactive schema diffs.

Create synthetic FHIR Observation and DiagnosticReport JSON documents containing both valid and intentionally invalid elements. Starter examples below are synthetic. They are not downloaded records.

HL7 FHIR overview Adopts FHIR StructureDefinition rules governing element optionality, cardinality, datatypes, and narrative metadata.

dspy, pydantic, fastapi. DSPy compiles robust prompt programs to inspect ambiguous JSON conformance violations and generate structured fix instructions. Local or hosted LLM with prompt evaluation support for strict validation rule synthesis.

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.

Flags missing mandatory FHIR metadata elements including status and code.

Verifies compliance with StructureDefinition cardinality constraints.

Emits machine-readable validation scorecards and suggested corrections.

```json [ { "input": { "resourceType": "Observation", "id": "obs-001", "status": "final", "code": { "coding": [ { "system": "http://loinc.org", "code": "48018-6" } ] } }, "expected_output": { "valid": true, "errors": [], "conformance_score": 1, "human_review_required": false } }, { "input": { "resourceType": "Observation", "id": "obs-002", "code": {} }, "expected_output": { "valid": false, "errors": [ "Missing required field: status", "Coding array is empty in code attribute" ], "conformance_score": 0.33, "human_review_required": true } } ] ```

Research informatics conformance verification tool without live clinical EHR connections. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Research informatics conformance verification tool without live clinical EHR connections. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Flags missing mandatory FHIR metadata elements including status and code. Verifies compliance with StructureDefinition cardinality constraints. Emits machine-readable validation scorecards and suggested corrections.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest FHIR JSON resources representing molecular and genomic observations. Validate required element cardinality and terminology bindings against FHIR R5 specifications. Detect missing data types, invalid code systems, or malformed narrative sections. Produce an interoperability audit report with remediation instructions.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Flags missing mandatory FHIR metadata elements including status and code. Verifies compliance with StructureDefinition cardinality constraints. Emits machine-readable validation scorecards and suggested corrections.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Interactive browser portal presenting conformance issues with interactive schema diffs.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Research informatics conformance verification tool without live clinical EHR connections.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest FHIR JSON resources representing molecular and genomic observations.

  • Validate required element cardinality and terminology bindings against FHIR R5 specifications.

  • Detect missing data types, invalid code systems, or malformed narrative sections.

  • Produce an interoperability audit report with remediation instructions.

Resources and assets

Reference links and supporting material

Dataset notes

Create synthetic FHIR Observation and DiagnosticReport JSON documents containing both valid and intentionally invalid elements. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

DSPy

Prompt and LM program optimization framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest FHIR JSON resources representing molecular and genomic observations. Validate required element cardi...
  • Flags missing mandatory FHIR metadata elements including status and code. Verifies compliance with Structur...
  • Interactive browser portal presenting conformance issues with interactive schema diffs.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 3 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

Action Space
  • DSPy · Optional
Training Infra
  • DSPy · Optional
Orchestration
  • DSPy · 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.

Frequently Asked Questions about Build a FHIR StructureDefinition Conformance and Sequence Evidence Auditor