Stream: argonaut
Topic: DocumentReference operation
Eric Haas (Dec 22 2016 at 22:29):
The Argonaut data query team defined an operation for DocumentReference in the Argonaut-DSTU2 Implemenation Guide. However, I haven't gotten much feedback on it and since I don't have the ability to test it out on server, I would like to get some here. Feedback on the operation itself and how its defined, technical edits, not the use case.
John Moehrke (Dec 23 2016 at 12:57):
Why did you make an operation for this? It is a simple REST query on DocumentReference? It would seem making an operation is more complexity with less flexibility.
John Moehrke (Dec 23 2016 at 13:00):
I ask so that I can understand and provide better feedback.
Grahame Grieve (Dec 23 2016 at 19:10):
the operation has a feature that the search doesn't have - sort of.
Grahame Grieve (Dec 23 2016 at 19:10):
the operation prompts the server to consider creating document references for the patient.
Grahame Grieve (Dec 23 2016 at 19:10):
where as search is looking for documents that already exist
Grahame Grieve (Dec 23 2016 at 19:11):
though you won't find it documented anywhere expliicitly that search is only for that. But it's details point against it's use for managing on-demand documents
John Moehrke (Dec 24 2016 at 15:08):
That is not the same pattern as on-demand documents in XDS. The DocumentReference exists, it is the document that does not yet exist. It would be the GET on the document URL that would 'create' a new document. But given that hint, I could see how this operation is asking for a document with the given constants to be created. Thus the constraints get to be defined by the client. In XDS on-demand the constraints are still defined by the server, the existence of the document content is just deferred until it is needed. This client side constraint system does appear to be able to control the time frame under which a summary is built. I would thus just question why that is considered a useful document? It might be technically logical, but medically it seems very suspect.
Eric Haas (Dec 28 2016 at 18:24):
When you do a Get for an DocuementReference you are looking for an pre-existing index and not asking the server to create one on the fly. In this use case neither the document nor the documentreference exists. ( but it can be generated) so you can not technically search for something that does not exist - you will get an empty bundle. The assumption is the documentreference reference will be used to fetch/generate the document on demand.
Last updated: Apr 12 2022 at 19:14 UTC
