FHIR Chat · Jan17Connectathon US-Core Track · implementers

Stream: implementers

Topic: Jan17Connectathon US-Core Track


view this post on Zulip Brett Marquard (Nov 01 2016 at 12:48):

This is the January 2017 Connectathon US-Core Track stream for discussion. Please send along any feedback.

view this post on Zulip Grahame Grieve (Jan 14 2017 at 15:23):

is there an agreed way for a server to indicate what patients clients should test with? a spreadsheet somewhere?

view this post on Zulip Brett Marquard (Jan 14 2017 at 15:41):

We just added an excel file for folks to attest which searches they support and provide patient ids US Core Tracker

view this post on Zulip Jenni Syed (Jan 14 2017 at 15:52):

For DiagnosticReport, shouldn't the date example params be le/ge? Not a list of equals tests? IE: a range rather than an exact date?

view this post on Zulip Nagesh Bashyam (Jan 14 2017 at 16:38):

If we supported the le and ge concepts, then we should be able to narrow down to the report that the provider/App or others are looking for
I am agreeing with Jenni that it is better to support "le" and "ge"
than the "eq"

view this post on Zulip Jenni Syed (Jan 14 2017 at 19:32):

I think the MU 3 CCDS requests a date range rather than a single date as well

view this post on Zulip Jenni Syed (Jan 15 2017 at 16:40):

May want to review the paragraphs here: http://build.fhir.org/medicationstatement-definitions.html#MedicationStatement to make sure they jive with the "active" query

view this post on Zulip Michelle (Moseman) Miller (Jan 15 2017 at 16:46):

FYI, I have a pending GF#12470 to update/fix that paragraph in MedicationStatement (the paragraph was added due to tracker GF#8010, logged against DSTU2, which had different element names, element types, and value sets than STU3 now supports).

view this post on Zulip Jenni Syed (Jan 15 2017 at 16:47):

I think what I'm struggling with is "snapshot in time" vs. the stuff in there that discusses "never"

view this post on Zulip Jenni Syed (Jan 15 2017 at 16:48):

So, for all orders in completed/error/past statuses - should notTaken always be 'Y' - they're not currently taking it... it may have been taken in the past

view this post on Zulip Jenni Syed (Jan 15 2017 at 16:48):

and if it is a snapshot in time... nottaking? (taking?)

view this post on Zulip Jenni Syed (Jan 15 2017 at 16:49):

because that taken status could change every time you take compliance...

view this post on Zulip Danielle Friend (Jan 15 2017 at 16:49):

Would it be more appropriate to have a flag of "isTaking" vs "hasNotTaken" which implies history not current compliance by the patient.

view this post on Zulip Jenni Syed (Jan 15 2017 at 16:50):

yes, i think that's where I'm struggling now, especially that we have more statuses and are saying that med statement is the "current list"

view this post on Zulip Jenni Syed (Jan 15 2017 at 16:54):

@Michelle (Moseman) Miller @Melva Peters I feel like we've discussed the notTaken vs notTaking naming in the past... I can't remember the discussion history

view this post on Zulip Jenni Syed (Jan 15 2017 at 16:55):

I do know we've always said this is a "snapshot in time" - so it feels wrong to try to represent the entire history of the order with that flag as it is right now


Last updated: Apr 12 2022 at 19:14 UTC