Closed slagesse-epic closed 1 year ago
DocumentReference -> Composition Stable document vs on-demand stable and changes to the document
Note that the mapping from Composition to DocumentReference aligned with the PCC defined mapping is already in the FHIR core specification for DocumentReference and emphasized in MHD. The mapping table is more helpful for those going from Composition to XDS Document Entry (vs FHIR DocumentReference).
Contact Details
slagesse@epic.com
Is your feature request related to a problem? Please describe.
aIPS is currently very XDS focused. While this is helpful for XDS minded readers, readers that are not familiar with XDS and wish to implement an MHD compatible solution might find the frequent references to XDS concepts off-putting.
Describe the solution you'd like
I think it would be helpful to these readers to concisely explain the minimal concepts needed to exchange IPS with DocumentReference in aIPS in a way that allows them to avoid referencing external specifications. References to XDS and the HIE white paper can still be provided, but for readers that wish to work in a traditional XDS environment or accomplish advanced exchange.
For On-Demand vs Stable, example use cases for both would be helpful.
I also think a Profile of DocumentReference with the PCC mappings applies to IPS would be helpful.
Describe alternatives you've considered
No response
Additional context
No response
Code of Conduct