FHIR Chat · bug? · implementers

Stream: implementers

Topic: bug?

Vadim Peretokin (Mar 01 2016 at 01:51):

At the bottom of https://hl7-fhir.github.io/profiling.html#slicing, it mentions:

In this case, the "name" element in the target resource

but there isn't an element literally called "name" in https://hl7-fhir.github.io/observation-example-bloodpressure.xml.html. Is it implying the display/@value attribute?

Josh Mandel (Mar 01 2016 at 03:01):

Observation.code used to be called Observation.name. Looks like we missed a reference in updating. Will you file a gForge tracker item?

Vadim Peretokin (Mar 01 2016 at 04:09):

That makes sense. I've filed http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9651.

Josh Mandel (Mar 01 2016 at 04:14):

Thanks!

Vadim Peretokin (Mar 01 2016 at 04:40):

In https://hl7-fhir.github.io/profiling.html#discriminator, what does the @type mean:

When slicing elements with a choice of types, the discrimnator SHALL be "@type".

It's a bit out of the blue.

I've filed a typo on the discrimnator already as well.

Vadim Peretokin (Mar 01 2016 at 04:43):

Alright thought about it some more and it now makes sense, just could be worded a bit more intuitively

Vadim Peretokin (Mar 04 2016 at 03:41):

@Grahame Grieve why not use google site: search for the search function in the spec?

Grahame Grieve (Mar 04 2016 at 05:14):

Vadim: they inpose advertising on us, and it doesn't work in China, or several other countries

Vadim Peretokin (Mar 04 2016 at 05:47):

got it, thanks

Grahame Grieve (Mar 05 2016 at 00:23):

(deleted)

Vadim Peretokin (Mar 10 2016 at 03:49):

how come _text is defined on Resource and not DomainResource? DomainResource is the one that contains the narrative and a Resource might not

Lloyd McKenzie (Mar 10 2016 at 07:22):

Can you raise that as a tracker item?

Vadim Peretokin (Mar 10 2016 at 22:04):

Yep, http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9701

Vadim Peretokin (Apr 11 2016 at 22:17):

I wonder where did the old bug? topic went. Anyway, what was the resolution in http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_id=677&tracker_item_id=9792? I don't see anything new in the repository.

Vadim Peretokin (Apr 11 2016 at 22:18):

okay, weird, it's still here, but the search and the dropdowns didn't see it

Grahame Grieve (Apr 12 2016 at 02:34):

Vadim, the id attribute of primitive elemenst goes in the name_ property, but not the id attribute of complex elements

Vadim Peretokin (Apr 12 2016 at 02:41):

I know. Have a look at https://hl7-fhir.github.io/media-example.xml.html though - <content id="a1"> . Content is of type Attachment, and there is no Attachment.id, but there is Element.id, so it is for the primitive element as far as I see. Happy to be corrected

Vadim Peretokin (Apr 12 2016 at 02:41):

Corresponding JSON lists it as

  "content": {
    "id": "a1",

Grahame Grieve (Apr 12 2016 at 02:42):

attachment is not a primitive

Vadim Peretokin (Apr 12 2016 at 02:42):

Hmm okay I see what you're getting at.

Ashish Sharma (Apr 12 2016 at 04:27):

I am getting the following message from the Test Page, 1.4 with DSTU 3 resources
Error: org.hl7.fhir.dstu3.model.Conformance cannot be cast to ca.uhn.fhir.model.base.resource.BaseConformance

Grahame Grieve (Apr 12 2016 at 04:32):

from which test page?

Vadim Peretokin (Apr 12 2016 at 07:37):

Okay not clear actually, spec says "Elements, and complex datatypes (types that contain named elements of other types) are represented using a JSON object, containing a member for each element in the datatype. Composites can have id attributes, which are converted to JSON member values, in the same manner as described for primitives.". Is a composite a complex datatype? That word is only used once on the page without a definition. If it is, isn't it saying id is treated same as complex types?

Lloyd McKenzie (Apr 12 2016 at 15:19):

I'd submit a change request for us to change "Composites" to "Complex data types"

Vadim Peretokin (Apr 12 2016 at 18:51):

Thanks Llyod. So is the text "Complex data types can have id attributes, which are converted to JSON member values, in the same manner as described for primitives" correct?