The CDISC lab semantics in FHIR Implementation Guide in action
summary
Demo converts Excel exports from local labs into 11 FHIR resources using a graphical drag-and-drop mapper and MuleSoft tooling, then composes a single CDISC LAB XML output for sponsor systems. Transformation runs on a local file system with scatter-gather parallel processing to speed resource creation. Mapping follows the CDISC Lab Semantics in FHIR IG, required fields only, validation is manual against Inferno for the demo, and the end-to-end pipeline runs and reduces manual transcription errors.
AI-written summary · about
chapters (15)
- 0:00Introduction and speakers
- 1:06Agenda and disclaimer
- 2:12Purpose of the implementation guide
- 3:18What is the lab semantics IG
- 4:03Centralized vs decentralized trials
- 5:49Data flow and FHIR's role
- 7:33Implementation details and demo setup
- 9:38Demo walkthrough and transformation
- 12:29Lessons learned from implementation
- 13:52Conclusion and potential impact
- 16:41Q&A session begins
- 17:03Machine-generated data in trials
- 18:33Auditability and traceability in data
- 20:18Validation of FHIR resources
- 21:44Mapping other data formats to FHIR
related talks
18mTranslating Tabular Data Maps into a FHIR Implementation Guide
47mMapping FHIR to OMOP Using Open Source Tools
46mCreate an Implementation Guide with FHIR Shorthand
46mStreamlining health data collection with FHIR at Sciensano
02h 10mLet's Build: Introduction Firely .NET SDK for FHIR
36mTransforming HL7 version 2 to FHIR
47mFHIR Questionnaires and Structured Data Capture
39mFHIR Implementation Guides benefits for developers