FHIR Chat · DocumentReference Date · implementers

Stream: implementers

Topic: DocumentReference Date


view this post on Zulip Drew Torres (Jul 15 2020 at 19:43):

@John Moehrke What is the intent of DocumentReference.Date? Is it intended to represent the initial DocumentReference creation date, or the date that this version was created?

view this post on Zulip Drew Torres (Jul 15 2020 at 19:49):

Part of the problem is how DSTU2 created and index were 2 fields, but now we only have date.

view this post on Zulip Drew Torres (Jul 15 2020 at 19:50):

The definition is a bit vague.

view this post on Zulip John Moehrke (Jul 15 2020 at 20:02):

There is no mapping to XDS for the .date field. So it is not used in my world. I really don't know why it is there. The .content.attachment.creation is where the creation dateTime of the document bits. And .lastUpdated would cover last updated. So All that is left is the creation of the DocumentReference resource. I would be happy to entertain a CR to remove it.

view this post on Zulip Drew Torres (Jul 15 2020 at 20:02):

LOL that would really tick people off because we have to implement this field for us-core.

view this post on Zulip Drew Torres (Jul 15 2020 at 20:03):

We are having a hell of time mapping it now.

view this post on Zulip John Moehrke (Jul 15 2020 at 20:05):

why would that tick people off... it certainly would not hurt people that are not understanding it... so whoever might be mad, should tell us what the new definition should be.

view this post on Zulip John Moehrke (Jul 15 2020 at 20:05):

note that OO block vote outstanding has major breaking changes...

view this post on Zulip Drew Torres (Jul 15 2020 at 20:08):

Well the regulation calls out us-core IG to implement, and US-Core has documentreference.date as being must support.

view this post on Zulip Drew Torres (Jul 15 2020 at 20:09):

We may end up having to add a new column just for this field because we don't support this field.

view this post on Zulip John Moehrke (Jul 15 2020 at 20:11):

well, who set it to MS? Why did they do that? Why did no comment complain that MS was on an element that people didn't know how to fill?

view this post on Zulip Drew Torres (Jul 15 2020 at 20:13):

I know at the time I didn't look at it as closely as I should have, and was in surgery during voting time to vote on the ballot.

view this post on Zulip John Moehrke (Jul 15 2020 at 20:14):

well.. I tried to get US-Core to just use IHE-MHD... which would have made this more clear... but I lost that argument too.

view this post on Zulip Drew Torres (Jul 15 2020 at 20:15):

Well both you and I wanted to merge DiagnosticReport and DocumentReference....

view this post on Zulip Vassil Peytchev (Jul 15 2020 at 20:26):

Based on the description, it seems to represent the timestamp of when the resource instance was created, not a version-specific creation timestamp...

view this post on Zulip John Moehrke (Jul 15 2020 at 20:27):

that is the best I came to. the creation timestamp for the DocumentReference resource itself

view this post on Zulip John Moehrke (Jul 15 2020 at 20:27):

which was kind of the same meaning of .indexed element....

view this post on Zulip John Moehrke (Jul 15 2020 at 20:28):

with the purpose of this being when the DocumentReference was first known to that FHIR Server

view this post on Zulip Vassil Peytchev (Jul 15 2020 at 20:41):

.indexed is the alternate name for it.


Last updated: Apr 12 2022 at 19:14 UTC