Introduction to FHIR for HL7 v2 experts
summary
Compares HL7 v2 concepts to concrete FHIR features and shows the spec live (hl7.org) and a US Core implementation guide example in JSON/XML, highlighting that FHIR enforces an 80/20 rule for resource fields, adds a mandatory logical identifier (resource primary key), and requires publicly published definitions for any extensions registry entries. Covers terminology: code system vs value set, profiling/conformance tooling, and why the hard part is mapping messaging semantics to RESTful state rather than field-level differences.
AI-written summary · about
chapters (10)
- 0:00Introduction to speaker
- 1:02V2 and FHIR comparisons
- 5:13Resource identities
- 9:37Navigating the FHIR spec
- 14:41Human readable and data
- 17:38Terminology and coding
- 21:35Conformance and governance
- 25:10Security and implementation
- 27:20Messaging vs. REST
- 30:55Q&A and session conclusion
