Stream: Covid-19 Response
Topic: Lantana tested with...?
Michael Donnelly (May 15 2020 at 17:19):
@Sean McIlvenna which servers were you able to test with?
- Audacious Inquiry
- Epic
- NextGen
- Symptomatic
Sean McIlvenna (May 15 2020 at 17:20):
Audacious Inquiry, for sure
Sean McIlvenna (May 15 2020 at 17:20):
and the covid19-on-fhir server
Sean McIlvenna (May 15 2020 at 17:20):
didn't try with others, but highly likely they'd work fine as long as the have Location and MeasureReport data
Michael Donnelly (May 15 2020 at 17:22):
Do you have time to give it a shot with NextGen and/or Epic and/or Symptomatic?
Michael Donnelly (May 15 2020 at 17:24):
Symptomatic: https://saner.symptomatic.io/baseR4/MeasureReport
Sean McIlvenna (May 15 2020 at 17:33):
NextGen: Almost works. It queries for MeasureReports just fine. However, our UI allows the user to select a specific Location to filter the MeasureReports by, and the Location selection screen uses "name:contains" to search for locations. It appears that NextGen does not support :contains. Our app would work 100% if NextGen's server supported "name:contains". Otherwise, I would have to modify our app to support only "name=XXX", but the user experience would not be as nice.
Sean McIlvenna (May 15 2020 at 17:35):
Epic's does not work because they don't seem to support Location at all. Just get a 404 when hitting /Location
Sean McIlvenna (May 15 2020 at 17:35):
and it is critical to the user to be able to filter MeasureReports by Location
Sean McIlvenna (May 15 2020 at 17:36):
sadly, Symptomatic does not work because they do not implement /metadata, and the HAPI FHIR client requires /metadata.
Sean McIlvenna (May 15 2020 at 17:37):
So, my assumption was incorrect. But, pretty close on some of them.
Nick Rupley (May 15 2020 at 17:37):
@Sean McIlvenna Try NextGen's again? I enabled name:contains on Location
Sean McIlvenna (May 15 2020 at 17:37):
trying now
Sean McIlvenna (May 15 2020 at 17:39):
ok, NextGen's works, though there is data issues
John Moehrke (May 15 2020 at 17:40):
Sean McIlvenna said:
NextGen: Almost works. It queries for MeasureReports just fine. However, our UI allows the user to select a specific Location to filter the MeasureReports by, and the Location selection screen uses "name:contains" to search for locations. It appears that NextGen does not support :contains. Our app would work 100% if NextGen's server supported "name:contains". Otherwise, I would have to modify our app to support only "name=XXX", but the user experience would not be as nice.
So are you requiring that MeasureReport.subject is a reference? that is it can't be a identifier? Is this a requirement of SANER, soeems SANER is requiring .identifier and not .reference
Sean McIlvenna (May 15 2020 at 17:40):
for example, one of the MeasureReports references a subject of Location/eILwZ2Ms9IkRo37PSgHnFzw3, and that location does not actually exist
Sean McIlvenna (May 15 2020 at 17:40):
our application does assume that MeasureReport.subject is a reference
Nick Rupley (May 15 2020 at 17:41):
Hmm, that might have been a MeasureReport that was ad-hod created by one of the other clients? Let me know what MeasureReport that is and I'll take a look
John Moehrke (May 15 2020 at 17:41):
shocking that a test server would have test results that are garbage.. shocking
Nick Rupley (May 15 2020 at 17:47):
I think I found the missing Location in question and created it, so that should be resolved now
Michael Donnelly (May 15 2020 at 17:48):
Sean McIlvenna said:
for example, one of the MeasureReports references a subject of Location/eILwZ2Ms9IkRo37PSgHnFzw3, and that location does not actually exist
That's an ID from Epic.
Michael Donnelly (May 15 2020 at 17:48):
Nick Rupley said:
Hmm, that might have been a MeasureReport that was ad-hod created by one of the other clients? Let me know what MeasureReport that is and I'll take a look
Probably one of ours that got pushed to you.
Nick Rupley (May 15 2020 at 17:48):
Hah, yeah probably we (or someone) pulled a MeasureReport from Epic and pushed to us
Michael Donnelly (May 15 2020 at 17:48):
(By someone else.)
Nick Rupley (May 15 2020 at 17:49):
I guess it would make sense to do some validation on a MeasureReport create/update to make sure the referenced Location/Organization actually exists huh
Sean McIlvenna (May 15 2020 at 17:54):
this is the core requirements for nandina:
- Location
- MeasureReport
- Location "name" search parameter with ":contains" modifier
- MeasureReport "date" search parameter
- MeasureReport "subject" search parameter
- MeasureReport references a Location
Sean McIlvenna (May 15 2020 at 17:55):
if those things are supported by the FHIR server, Nandina will work with it
Last updated: Apr 12 2022 at 19:14 UTC
