Stream: implementers
Topic: DocumentReference _lastUpdated
Jay Gustafson (Aug 17 2020 at 15:18):
We are trying to use the _lastUpdated parameter, but have not seen it make a difference on our DSTU2 endpoints. Does anyone know which EHRs are using _lastUpdated for the DocumentReference call?
Lloyd McKenzie (Aug 23 2020 at 23:10):
If you query their CapabilityStatement, they should declare what SearchParameters they support
Jay Gustafson (Aug 24 2020 at 22:15):
Yes, some use "period" or "date" instead of "_lastUpdated". We're having trouble getting those search parameters to work too.
Lloyd McKenzie (Aug 24 2020 at 23:34):
period and date are quite different from _lastUpdated
Lloyd McKenzie (Aug 24 2020 at 23:34):
Can you expand on what trouble you're having?
Jay Gustafson (Aug 25 2020 at 16:18):
The first time we call DocumentReference?patient=1234 to get all the docs on say 2020-08-01. Then, the next time the user comes back to import data, we'd like to only get the docs that are new since the last pull: DocumentReference?patient=1234&period=ge2020-08-01. It still returns all of the documents.
John Moehrke (Aug 25 2020 at 16:28):
that sounds like a server failure. did the server declare in the CapabilityStatement support for period query parameter?
Michele Mottini (Aug 25 2020 at 16:50):
...did you try DocumentReference?patient=1234&_lastUpdated=ge2020-08-01 ?
John Moehrke (Aug 25 2020 at 16:57):
Michele Mottini said:
...did you try
DocumentReference?patient=1234&_lastUpdated=ge2020-08-01?
right, that would be more correct paging... and rely less on the odd math that is comparison on periods
Jay Gustafson (Sep 03 2020 at 23:25):
I've consulted the capability statement and tried both parameters.
Last updated: Apr 12 2022 at 19:14 UTC
