Place up to three profiles side by side. Compare their architectural role, lifecycle reach, and first limitation to test. No single standard covers every layer.
Working set
Choose profiles
1 of 3 selected
01
IPSStandard
Decision lens
Compare roles before choosing an implementation.
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
01
Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
02
Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
03
Test the boundary
Read what each option leaves unresolved before judging maturity or implementation fit.
Assessment
Review lifecycle coverage and practical fit.
Read left to right. Lifecycle reach comes first; a maturity label never overrides a scope mismatch.
01 · Lifecycle reach
Where each profile contributes directly
Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.
Readiness-stage coverage for International Patient Summary
No direct role is recorded for Plan, Learn + reuse.
Known limitation
ISO 27269 does not define the summarization workflow, and the HL7 guide remains STU, is based on FHIR R4, and permits national derivations. A patient summary is a curated snapshot, not a longitudinal warehouse.
03 · Detailed assessment
Check the fit and source behind the map
Use the official source, version, and limitation together. A higher maturity label does not erase a scope mismatch.
Detailed comparison of International Patient Summary
A concise, specialty-agnostic core patient summary and FHIR document profiles for essential clinical information such as problems, allergies, medications, results, procedures, and provenance.
Best fitCross-border or unscheduled care, patient-mediated exchange, continuity-of-care summaries, and bounded clinical or research handoffs that need a named minimum-content contract.
Readiness stages
AcquireHarmonizeExchange
AI-ready contribution
A consistent summary improves retrieval and feature alignment, but omission rules, stale content, source provenance, reconciliation quality, and summarization bias can materially affect models.
First limitation to test
ISO 27269 does not define the summarization workflow, and the HL7 guide remains STU, is based on FHIR R4, and permits national derivations. A patient summary is a curated snapshot, not a longitudinal warehouse.
Maturity
Scaling
Published ISO core dataset with a current HL7 FHIR R4 implementation guide at STU2