FHIR Chat · binary patient/subject link? · implementers

Stream: implementers

Topic: binary patient/subject link?


view this post on Zulip Drew Torres (Apr 24 2019 at 13:56):

Is there a reason why binary doesn't support patient/subject nor any query parameters?

view this post on Zulip Lloyd McKenzie (Apr 24 2019 at 14:38):

Metadata about a Binary is conveyed with Media or DocumentReference. The Binary is just the file - a JPEG or a PDF sitting on a harddrive with no metadata other than what you could get from the hard drive (size and mime type).

view this post on Zulip Lloyd McKenzie (Apr 24 2019 at 14:38):

That's what allows you to POST and GET as a raw binary.

view this post on Zulip Drew Torres (Apr 24 2019 at 17:41):

What resource is appreciate then to store non media type of raw content? An example may be, I want to store a certificate in relation to patient resource.

view this post on Zulip Lloyd McKenzie (Apr 24 2019 at 19:13):

DocumentReference

view this post on Zulip Drew Torres (Apr 24 2019 at 19:14):

Isn't that overloading DocumentReference?

view this post on Zulip Lloyd McKenzie (Apr 24 2019 at 20:07):

We're looking at renaming it. But the consensus is, based on changes to Media and Observation is that DocumentReference is the mechanism to communicate metadata about anything that isn't 'media'.

view this post on Zulip Drew Torres (Apr 24 2019 at 20:51):

Fair enough. I assume then scope would also have to change for document reference.

view this post on Zulip Drew Torres (Apr 24 2019 at 20:52):

Is there already a tracker for that?

view this post on Zulip Lloyd McKenzie (Apr 24 2019 at 21:16):

I thought so, but I can't find it. If you want to submit a new one, that wouldn't be a bad idea.

view this post on Zulip Drew Torres (Apr 25 2019 at 17:10):

Logged: https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=20973&start=0

view this post on Zulip John Moehrke (Apr 26 2019 at 16:23):

There is no requirement today that DocumentReference is patient specific. Can you please clarify what parts of the scope you want changed and what you recommendation of new wording is?

view this post on Zulip Drew Torres (Apr 30 2019 at 14:33):

A DocumentReference resource is used to index a document, clinical note, and other binary objects to make them available to a healthcare system. A document is some sequence of bytes that is identifiable, establishes its own context (e.g., what subject, author, etc. can be displayed to the user), and has defined update management. The DocumentReference resource can be used with any document format that has a recognized mime type and that conforms to this definition.

view this post on Zulip Drew Torres (Apr 30 2019 at 14:33):

It implies it is a document, but not really.

view this post on Zulip John Moehrke (Apr 30 2019 at 15:02):

what is your recommended new wording?

view this post on Zulip Drew Torres (Apr 30 2019 at 15:08):

Depends on what is landed on the new resource name is. I would say something like:

A <NEW_RESOURCE> resource is used to index binary objects to make them available to a healthcare system. A <NEW_RESOURCE> is some sequence of bytes that is identifiable, establishes its own context (e.g., what subject, author, etc. can be displayed to the user), and has defined update management. The <NEW_RESOURCE> resource can be used with any binary data.

view this post on Zulip Drew Torres (Apr 30 2019 at 15:09):

I haven't looked at the entire page either. That was just the first place that throws me off for the new defined resource.


Last updated: Apr 12 2022 at 19:14 UTC