Stream: implementers
Topic: extensions Patient Name Parts
Joel Francis (Aug 30 2017 at 19:29):
Hi,
I have a couple of questions regarding the example 2.5.2.2 Patient Name Parts in the specification.
1. I noticed that the <element> for Extension.url was missing in the example. It is safe to represent this as a fixedURI which in all cases should reference the StructureDefinition that define the extension?
Ex: <element>
<path value="Extension.url">
<min value="1"/>
<max value="1"/>
<fixedUri value="http://www.testing.com/StructureDefinition/name-qualifier"/>
</element>
Here fixedUri is the same as the Uri for the StructureDefinition that is defining this extension
2. On the notion of context can
<context value="HumanName.given" />
<context value="HumanName.prefix" />
<context value="HumanName.family" />
<context value="HumanName.suffix" />
be replaced by just <context value="This extension can be used anywhere a HumanName.part appears" />
Lloyd McKenzie (Aug 30 2017 at 20:43):
1. The example should indeed include a fixed value for the url. Can you please submit a change request for us to address that?
2. Context must be a specific Resource path. It's computable. (So "no" :))
Joel Francis (Aug 30 2017 at 22:32):
Thanks @Lloyd McKenzie . I need a clarification for the 2nd point. So the value of the url should be a path to the base/core StructureDefinition of the resource/datatype in context?
Also thinking about the example 2.5.2.1.2 which is different from the one above, it too is missing a url value. it goes directly into creating a valueUri which is extremely confusing eyes spinning. Can you please clarify and advise?
Lloyd McKenzie (Aug 31 2017 at 02:36):
Yes, that example is wrong too. Please submit a change request to fix the examples as well.
Joel Francis (Aug 31 2017 at 02:40):
Yes, that example is wrong too. Please submit a change request to fix the examples as well.
Thanks @Lloyd McKenzie . Can you refer me to a page on how to request these changes?
Grahame Grieve (Aug 31 2017 at 02:50):
at the bottom of every page in the spec - "Propose a change": http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemAdd&tracker_id=677
Lloyd McKenzie (Aug 31 2017 at 02:51):
You'll need to register initially - we have a human review step to check for Viagra sales-people, but it's free. Once you're registered you can submit as many change requests as you like.
Joel Francis (Aug 31 2017 at 14:32):
Thanks @Grahame Grieve and @Lloyd McKenzie
Joel Francis (Sep 06 2017 at 13:38):
You'll need to register initially - we have a human review step to check for Viagra sales-people, but it's free. Once you're registered you can submit as many change requests as you like.
You'll need to register initially - we have a human review step to check for Viagra sales-people, but it's free. Once you're registered you can submit as many change requests as you like.
@Lloyd McKenzie https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13794
Lloyd McKenzie (Sep 06 2017 at 13:40):
Great
Last updated: Apr 12 2022 at 19:14 UTC
