Stream: implementers
Topic: Standard Extensions and Profiles
Peter Bernhardt (Jun 13 2016 at 19:16):
Basic question. How does an implementer express support for a standard extension that may not be formally included in a profile? Something like patient-birthTime, for example. Would it be legal to say this conforms to the Patient profile? Or does it need further qualification?
Lloyd McKenzie (Jun 13 2016 at 21:14):
Your Conformance statement should point to resource-specific profiles that identify the data elements (core + extension) that you're capable of handling.
Peter Bernhardt (Jun 13 2016 at 21:16):
@Lloyd McKenzie is there a cross reference for standard extensions and existing profiles?
Peter Bernhardt (Jun 13 2016 at 21:17):
for example, i should be able to go from patient-mothersMaidenName to the DAF Patient profile
Dave Carlson (Jun 13 2016 at 21:24):
@Peter Bernhardt interesting question about extension cross-reference. It seems to me that this could only be done in the context of a profile repository (e.g. HL7 balloted artifacts, or other organization specific repository). Extensions may be specified on any resource independent of profile, so you'd need to index all known extensions and profiles.
Peter Bernhardt (Jun 13 2016 at 21:31):
@Dave Carlson yes, such a repository would be essential as profiles proliferate and we run the risk of duplication. In the meantime, for standard extensions and profiles covered in the FHIR docs I was hoping to save a bit of time in looking through the spec.
Dave Carlson (Jun 13 2016 at 21:35):
So the "repository" in this case is all HL7 balloted extensions and profiles. It would need to be integrated into HL7 build and publishing. To generalize, would be best to implement as a secondary analysis of all published StructureDefinition files. Unfortunately, I've never seen such an analysis.
Michel Rutten (Jun 13 2016 at 21:50):
Interesting discussion. We're certainly aiming to implement useful features such as cross references into our FHIR profile registry at http://simplifier.net. All content is stored in a FHIR server and indexed, so the technical foundation is already in place.
Peter Bernhardt (Jun 13 2016 at 21:59):
@Michel Rutten pretty close to what I was thinking about. Thanks.
Lloyd McKenzie (Jun 13 2016 at 23:15):
@Peter Bernhardt The most we could do in the HL7 publication is to cross-link to those profiles HL7 publishes with the spec - which will be a declining set. You're free to submit a change request asking for that though. Agree that the long-term solution is cross-references in tools like simplifier.net
Last updated: Apr 12 2022 at 19:14 UTC
