FHIR Chat · Problem in R4 structure definitions?

Stream: implementers

Topic: Problem in R4 structure definitions?

Michele Mottini (Oct 02 2018 at 16:32):

...looking at the R4 profile-types.xml I found a couple of things that seem wrong

Michele Mottini (Oct 02 2018 at 16:32):

At line 154:

Michele Mottini (Oct 02 2018 at 16:33):

      <element id="Element.id">
        <path value="Element.id"/>
        . . .
      <!-- Note: primitive values do not have an assigned type. e.g. this is compiler magic. XML,
JSON and RDF types provided by extension -->
        <type>
          <code>
            <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-json-type">
              <valueString value="string"/>
            </extension>

Michele Mottini (Oct 02 2018 at 16:33):

but Element.id is not a primitive value

Michele Mottini (Oct 02 2018 at 16:34):

Same thing for Extension.Url

Michele Mottini (Oct 02 2018 at 16:36):

Another thing: all the primitive values referenced to themselves as base:

Michele Mottini (Oct 02 2018 at 16:36):

      <element id="integer.value">
        <base>
          <path value="integer.value"/>
          <min value="0"/>
          <max value="1"/>
        </base>

Michele Mottini (Oct 02 2018 at 16:37):

that seems wrong as well

Grahame Grieve (Oct 02 2018 at 20:02):

first -they are primitive values

Grahame Grieve (Oct 02 2018 at 20:02):

second - please make a task

Michele Mottini (Oct 02 2018 at 20:38):

Mhh...no, Element.id is not the same thing as boolean.value: it is OK for the second not to have a type (its type is boolean!), but Element.id most definitely has one - string