Lab Automation Product Catalog Standardizer with FHIR and OMOP Models
Integrating new lab products across clinical networks requires mapping hardware and reagent SKUs into standardized healthcare data schemas. You will build an automated mapping engine using Python, FHIR resources, and OMOP CDM to normalize vendor device payloads, achieving 95% mapping accuracy.
What you are building
The core problem, expected build, and operating context for this challenge.
Construct an OMOP/FHIR standardization data pipeline in Python to normalize laboratory automation equipment and reagent catalogs.
How work is evaluated
Evaluates FHIR resource generation validity and OMOP concept mapping accuracy.
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.
fhir_validity_check
Ensure output conforms to FHIR R4 Device schema
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
omop_concept_accuracy
Accuracy rate of matched OMOP concept IDs • target: 0.95 • range: 0-1
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Map proprietary lab equipment and assay product specs to FHIR Device and SpecimenDefinition resources
Standardize lab product terminology using OMOP CDM concept identifiers (LOINC, SNOMED)
Validate interoperability schemas against HL7 FHIR validation specifications
Reference links and supporting material
Lab product catalog dataset containing 300 vendor equipment and reagent entries.
Challenge setup
Evaluates FHIR resource generation validity and OMOP concept mapping accuracy.
Challenge input
JSON object with vendor, product_name, and catalog_number
FHIR Framework
Industry standard for health data exchange.
OMOP CDM
Standardized observational data model.
Evaluated output
JSON FHIR Device resource object with valid resourceType and codeableConcept
- Ensure output conforms to FHIR R4 Device schema
- Accuracy rate of matched OMOP concept IDs • target: 0.95 • range: 0-1
- Benchmark: InteropData-Bench
- Omop Concept Accuracy target: 0.95
- 1 public reference case
- Python execution harness
- Python sandbox (unavailable on Versalist)
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
- Zed · Required
- Durable · Optional
- Mistral Nemo · Optional
Evaluation contract
- fhir_validity_check · Weight 1
- omop_concept_accuracy · Weight 1
Metrics
- omop_concept_accuracy · Target 0.95
Benchmarks
- InteropData-Bench
- general
Reference cases
- 1 public reference case
Workflow tasks
- Task 1
Input: JSON object with vendor, product_name, and catalog_number
Output: JSON FHIR Device resource object with valid resourceType and codeableConcept
Execution harness: Python
Evaluation tools
- FHIR Framework · Healthcare Interoperability Schema
- OMOP CDM · Common Data Model
Recipe freeze marker
No recipe freeze time is recorded.