Leveraging US specifications for the world
summary
HL7 registries list about 165 implementation guides of which roughly 80 are labeled U.S. realm, 61 are global and ~22 are other countries, and registry.fire.org shows different counts (65 US, 40 international), so U.S. output dominates because of timing, market size and ONC/CMS regulation. Practical advice: prefer reusable terminologies, avoid tightly licensed codes like CPT, use concept maps or substitute identifier systems, inspect extensions and hidden business rules, and choose one of three adaptation patterns: supplemental delta, fork and edit, or patch/apply deltas. universal and internationalizable label strategies help.
AI-written summary · about
chapters (20)
- 0:00Introduction to talk
- 1:25Three key terms explained
- 4:37Why US standards dominate globally
- 7:25Benefits of adopting US specs
- 9:09Understanding realm and universal specs
- 12:20Handling terminology in specs
- 16:12Working with identifiers
- 18:18Evaluating extensions
- 19:41Business rules in specs
- 20:44Descriptions and examples
- 22:49Assessing implementation guides
- 23:51Architectural choices
- 25:34Targeting implementers
- 26:57Business model alignment
- 28:21Approaches to adapting specs
- 30:28Designing for international use
- 32:13Maintaining specification alignment
- 33:39Moving to international specs
- 33:59Language and localization
- 35:04Summary and key takeaways
related talks
25mUsing Open Source Technologies to Deliver a Healthcare...
26mAdvancing Interoperability, Patient Safety, and Efficiency ...
45mOSPOs & Transition Paths for Regulated Environments
53mCreating Standards - From Writing a Spec to Obtaining ISO Status
26mKeynote Day 1
45mRegulated and Sovereign : Impact to the Open Source Developer
30mOpen Source Is Making a Difference in Health Information Tech...
20mOpen Standards meets Open Source - Good Practice Guidance for Use of ISO19115-1