FHIR Chat · Addition of Reference.type · implementers

Stream: implementers

Topic: Addition of Reference.type


view this post on Zulip Grahame Grieve (Feb 24 2018 at 05:28):

We received no formal feedback about the addition of Reference.type. I'm going to go ahead and add it.

view this post on Zulip Grahame Grieve (Feb 24 2018 at 05:29):

but I propose adding it a little differently to that proposed, after thinking about it. I want to add it identically to the semantics of ElementDefinition.type.code

view this post on Zulip Lloyd McKenzie (Feb 24 2018 at 05:49):

Meaning it's allowed to point to a logical model?

view this post on Zulip Grahame Grieve (Feb 24 2018 at 06:50):

y

view this post on Zulip Grahame Grieve (Feb 26 2018 at 05:19):

it is valid to have this:

  "subject" : {
   "type" : "Patient"
  }

?

view this post on Zulip Lloyd McKenzie (Feb 26 2018 at 05:30):

Ick. Though I guess there are theoretical use-cases for it.

view this post on Zulip David Hay (Feb 26 2018 at 06:33):

Is this in an instance? ie referring to some unidentified patient?

view this post on Zulip Grahame Grieve (Feb 26 2018 at 06:34):

y

view this post on Zulip nicola (RIO/SS) (Feb 26 2018 at 06:48):

@Grahame Grieve is there draft of this changes somewhere?

view this post on Zulip Grahame Grieve (Feb 26 2018 at 08:27):

no, because I can't commit right now

view this post on Zulip Paul Knapp (Feb 26 2018 at 08:33):

Can it only be the name of a resource or any 'thing', also - is gforge down?

view this post on Zulip Grahame Grieve (Feb 26 2018 at 08:35):

in a resource, it can only be a defined resource type. And yes, gForge is down

view this post on Zulip Paul Knapp (Feb 26 2018 at 08:46):

Excellent, thank you for adding this - I'll check for where I can now remove elements inserted to address the absence of the type.

view this post on Zulip Grahame Grieve (Feb 27 2018 at 07:52):

@nicola (RIO/SS) build is up

view this post on Zulip Angus Millar (Sep 06 2019 at 01:08):

In FHIR R4 the newly added Reference.type property on the Reference datatype is stated to be of type Uri however it is bound to a value set of all the FHIR resource types. http://hl7.org/fhir/ValueSet/resource-types. Shouldn't this Reference.type property be of type code? How is Reference.type = Patient considered to be a Uri? Am I missing something?

view this post on Zulip Grahame Grieve (Sep 06 2019 at 01:13):

yes. it's extensible. See http://hl7.org/fhir/references.html#type:

In order to support Logical Models, the type element has the type of "uri". Whenever type appears in resources, the uri is represented relative to the base URI http://hl7.org/fhir/StructureDefinition/. For resources, then, the value is simply a code that is the type of resource - e.g. "Patient"

view this post on Zulip Angus Millar (Sep 06 2019 at 05:20):

Thanks @Grahame Grieve , I should have read on.


Last updated: Apr 12 2022 at 19:14 UTC