Stream: implementers
Topic: Condition across encounters
Mritunjay Dubey (Jun 09 2017 at 11:46):
Hello people,
In our systems we capture diagnosis and condition as two different entities.
The criteria for diagnosis is something which will be part of just one encounter, e.g.- a person diagnosed with cholera.
Conditions are the one which will be present across the encounters, e.g.- A person having diabetes. In first encounter it will be entered as a condition and in subsequest visits it will be marked as a followup to the condition.
We wanted to map both as condition but we are not sure how we will differintiate between after mapping. Can you guys help me knowing what could be right way to go about it ?
Lloyd McKenzie (Jun 09 2017 at 13:39):
Condition.category is intended for this purpose
John Moehrke (Jun 09 2017 at 13:42):
so is the addition of PractitionerRole something that will be done in bulk? Or does each workgroup need to stumble upon that it is missing in their Resources and add specific CR for each?
Lloyd McKenzie (Jun 09 2017 at 13:44):
Workflow will shortly be updating the patterns and seeking feedback from all work groups. (We're going to try to have a report available that shows deltas too.) After feedback, we'll adjust the patterns, then ask work groups to review their resources for alignment as makes sense for each resource
Mritunjay Dubey (Jun 14 2017 at 10:00):
Hey @Lloyd McKenzie Thanks for the help. I had one more question
In our systems there are 4 states of a condition
1) When the condition was entered in system => active condition
2) Since conditions are present across visits, in our systems the doctor can just say, this visit is the follow-up of an existing condition. => follow-up condition
3) Once the patient is cured of that problem we can mark a condition as history-of conditions of patient. This means the condition is inactive right now but this is important to know that patient had this problem at some point of time.
4) Inactive conditions
Is there a field which can accomodate these states ?
Michelle (Moseman) Miller (Jun 14 2017 at 13:34):
Condition.category is 0..* and has an example binding, which means you can have other category codes if you'd like.
Inactive conditions should be conveyed with the Condition.clinicalStatus = inactive (or resolved or remission if that distinction is known)
Lloyd McKenzie (Jun 14 2017 at 16:18):
Difference between "in history" and just "inactive" is handled by whether a Condition is included in a problem List instance.
Last updated: Apr 12 2022 at 19:14 UTC
