Stream: implementers
Topic: Question about $current-problems
Yunwei Wang (May 16 2019 at 02:33):
While reading https://www.hl7.org/fhir/lifecycle.html page, I am confused by the difference between Condition?_list=$current-problems and Condition?clinicalStatus=active&category=problem-list. Can someone clarify the difference?
Lloyd McKenzie (May 16 2019 at 03:09):
It's possible for a system to have records sent as part of referrals, documents, etc. that are retained for record-keeping purposes that aren't deemed to be part of the "active problem list" by a given system. Right now, EHRs aren't exposing that data - at least not using proper resources. But eventually it'll probably be necessary. Which is one of the reasons Grahame argued long and hard for Argonaut to use List for allergies, meds, conditions, etc.
Yunwei Wang (May 16 2019 at 03:49):
@Lloyd McKenzie Thank you for the explanation. It sounds really like so called "past medical history" in some EHR (which refers a list of clinically significant, resolved conditions). Is that correct?
Lloyd McKenzie (May 16 2019 at 03:50):
Or just "stuff collected from elsewhere". It might not be clinically significant - or even true - but it was shared at some point and thus is part of the record.
Yunwei Wang (May 16 2019 at 03:53):
Then why is it called "current"-problems?
Lloyd McKenzie (May 16 2019 at 04:05):
I was talking about what might come back from the query. The $current-problems would be a curated list that would exclude all of that other stuff.
Grahame Grieve (May 16 2019 at 12:32):
a condition resource that claimed to be current at the time - might still claim to be current in it's context - might not be current as far as the system is concerned. But making it necessary to hunt down and change all
Grahame Grieve (May 16 2019 at 12:33):
'current' status to some special status that means 'current in my context but not current now' is futile for several reasons, not least because context is implicit
Yunwei Wang (May 17 2019 at 00:56):
@Grahame Grieve Other than reading "current"problems, can I also update/move a problem to "current" list?
Grahame Grieve (May 17 2019 at 01:09):
I think right now, no. If we define the $add and $delete operations, then yes
Lloyd McKenzie (May 17 2019 at 01:37):
Main issue is that the EHRs (in the US at least?) aren't currently supporting the $current operations (or List generally) at all.
Grahame Grieve (May 17 2019 at 01:37):
right. they've just said the scope of the API is the list
Lloyd McKenzie (May 17 2019 at 01:41):
(Which then means that the API can't be used for any other use-case - and there are lots of other use-cases...)
Grahame Grieve (May 17 2019 at 01:44):
that's what they decided yes. they can always put up another end-point later
Brian Postlethwaite (Jun 08 2019 at 19:58):
Are we likely to add those new ops to list? $add and $delete?
Grahame Grieve (Jun 09 2019 at 00:54):
I thought we had. Was there a task?
Brian Postlethwaite (Jun 09 2019 at 17:33):
They aren't in the current build.
Brian Postlethwaite (Jun 09 2019 at 17:34):
I don't recall creating one.
Grahame Grieve (Jun 09 2019 at 18:26):
make one...
Last updated: Apr 12 2022 at 19:14 UTC
