International Patient Access (IPA) specification
summary
Specification defines a narrow patient-access baseline: IPA 1.0.0 published March, a subset of US Core that mandates JSON and profiles 9 main profiles plus three supporting profiles, zero extensions/terminologies, and a single operation docref operation to fetch documents (including CDA) or ask the server to compose an IPS. Security uses SMART-on-FHIR and leaves app certification to jurisdictions; several national IGs already derive from IPA and tooling supports direct dependency. Upcoming work adds finer-grained must-support/obligation semantics.
AI-written summary · about
chapters (17)
- 0:00Introduction and speaker background
- 1:06Purpose of FHIR implementation guides
- 2:32What is the IPA specification
- 3:57Apps and EHR integration vision
- 5:20Benefits of IPA for stakeholders
- 6:44IPA vs International Patient Summary
- 8:12Key ingredients of IPA
- 10:24DocRef operation explained
- 11:27IPA profiling work and profiles
- 13:11Applying IPA in national guides
- 14:37Must support and obligation extensions
- 17:30Summary and next steps
- 18:16Q&A: DocRef operation
- 20:27Q&A: EHR adoption and IPA
- 22:13Q&A: Resources and community involvement
- 22:33Call to action and resources
- 23:39Hands-on coding session
related talks
24mInternational Patient Access
43mGlobal Implementations with the International Patient Access
42mInternational Patient Summary
46mInternational Patient Summary (IPS) - Moving from Specification to Implementation
26mInternational Patient Summary: examples, tooling and exchange
49mIHE Profiles and FHIR (1)
23mThe Smart4Health project
01h 04mApisecure, 14 & 15 March 2023 - Grahame Grieve, Principal at Health Intersections Pty Ltd.