Stream: implementers
Topic: Summary fields and profiles
Sufyan Patel (Feb 07 2018 at 13:14):
I am interested in using the _summary function for the FHIR resources but my question is whether we can profile which elements we can set as a summary field.
The Forge tool currently doesn't allow it right now so I'm asking whether it's a simple case of adding
- <isSummary value="true" />* in the StructureDefinition?
John Moehrke (Feb 07 2018 at 14:36):
no, summary is defined in the definition of the Resource. You might find the _elements helpful http://build.fhir.org/search.html#elements
Sufyan Patel (Feb 07 2018 at 14:46):
I thought so. Can i define extensions in the elements field too?
Lloyd McKenzie (Feb 07 2018 at 15:08):
You can choose to bring all extensions at a given path but you can't currently filter by extension URL. If you need this, you could propose it as a change request using the "propose a change" link at the bottom of any page in the spec.
Grahame Grieve (Feb 07 2018 at 18:36):
this is where graphql comes in
Sufyan Patel (Feb 08 2018 at 12:35):
Done some more reading on https://www.hl7.org/fhir/search.html#summary and if i'm not mistaken, it states that a user can pick which fields can be summary fields. Is this to your understanding too?
Lloyd McKenzie (Feb 08 2018 at 15:18):
Summary can only be set when FHIR defines the resources. It can't be changed by profiles and can't be custom-configured by systems. Systems can choose whether to support summary queries at all, and they can choose what data elements they support. But if they support "summary" and they support a data element and HL7 has defined an element to be a summary element in the resource definition, then it must be returned in summary queries and no element that is not marked as summary is allowed to be returned.
Lloyd McKenzie (Feb 08 2018 at 15:19):
If you see wording in the spec that conflicts with this, please let us know where so we can make it clearer.
Last updated: Apr 12 2022 at 19:14 UTC
