ISiK specification and Patient-merge
summary
ISiK becomes legally binding for German HIS vendors at initial publication, and the base module is mandatory next month; hospitals report roughly 90% use of HL7 v2 ADT so any FHIR solution must interoperate with legacy ADT flows. There is no standard FHIR R4 operation to perform patient merges — no FHIR R4 merge operation — so options on the table are an MPI/MDM black box interface, adopting R5 merge features, or publishing an ISiK implementation guide that enforces encounter handling and expected merge semantics. Working groups start September 2023 to define requirements.
AI-written summary · about
chapters (5)
- 0:00Introduction and ISiK overview
- 2:12ISiK specification structure
- 7:15Patient merge problem definition
- 10:29Project status and next steps
- 15:30Q&A and closing
related talks
21mThe IsiK Project of the German National Digital Health Agency
49mIHE Profiles and FHIR (1)
46mPost-Acute Care Interoperability work group - outcomes
27mFHIR for delivery to quality registrations
22mConsent management in medical research with FHIR
41mFHIR workflow
41mMapping V2 to FHIR and back
21mTransitioning of Message Mapping Guide to FHIR Implementation Guide