FHIR Chat · build.fhir.org Datatype representation

Stream: committers

Topic: build.fhir.org Datatype representation

Andy Stechishin (Sep 06 2019 at 01:21):

Not sure if this belong here or in implementers (or maybe in tooling). At some point during the last 2-3 week the representation of some of the datatypes changes. In particular the the id attribute on the complex datatypes as demonstrated using the id on the Age datatype below

current:

{
      "id" : "Age.id",
      "path" : "Age.id",
      "representation" : ["xmlAttr"],
      "short" : "Unique id for inter-element referencing",
      "definition" : "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
      "min" : 0,
      "max" : "1",
      "base" : {
        "path" : "Element.id",
        "min" : 0,
        "max" : "1"
      },
      "type" : [{
        "extension" : [{
          "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fhir-type",
          "valueCode" : "string"
        }],
        "code" : "http://hl7.org/fhirpath/System.String"
      }],
      "isModifier" : false,
      "isSummary" : false,
      "mapping" : [{
        "identity" : "rim",
        "map" : "n/a"
      }]
    },

    {
      "id" : "Age.id",
      "path" : "Age.id",
      "representation" : ["xmlAttr"],
      "short" : "Unique id for inter-element referencing",
      "definition" : "Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.",
      "min" : 0,
      "max" : "1",
      "base" : {
        "path" : "Element.id",
        "min" : 0,
        "max" : "1"
      },
      "type" : [{
        "code" : "string"
      }],
      "isModifier" : false,
      "isSummary" : false,
      "mapping" : [{
        "identity" : "rim",
        "map" : "n/a"
      }]
    },

Was this change intended? I apologize if I missed the notification of this change occuring

Grahame Grieve (Sep 06 2019 at 01:27):

uh? the id hasn't changed. The type has

Andy Stechishin (Sep 06 2019 at 01:46):

Yes, the way that the type is described in the raw definition. I am guessing that this is how it will be done going forward

Grahame Grieve (Sep 06 2019 at 01:46):

yes. you can track the long discussion about this in the conformance thread

Grahame Grieve (Sep 06 2019 at 01:47):

I will be issuing technical corrections to R3 and R4 to align with this after Atlanta

Andy Stechishin (Sep 06 2019 at 01:47):

Ah, that is why I missed the change, I don't subscribe to that thread

Andy Stechishin (Sep 06 2019 at 01:48):

So you are backporting the definitional change to the existing R3 and R4? That would be helpful

Grahame Grieve (Sep 06 2019 at 01:53):

yes. the build is where we are looking at the outcome of our discussions, but it has always been about fixing up the R3 and R4 definitions

Andy Stechishin (Sep 06 2019 at 01:53):

Thanks Grahame, I figured I just missed the change somehow

Last updated: Apr 12 2022 at 19:14 UTC

Main menu

FHIR Chat · build.fhir.org Datatype representation · committers