Stream: implementers
Topic: Episode of care
Mounika (Oct 12 2018 at 13:24):
Hi all,
I need to create Episode of care Definitions which was taken from http://www.prometheusanalytics.net/deeper-dive/concepts-and-use. We want to capture these metadata (Trigger codes, Typical Diagnosis Codes, Typical Procedure Codes, Potentially Avoidable Complication Codes, Prescription Codes, Subtypes, Global E&Ms, Universal Risk Factors). Can anyone suggest me.
Thank you.
Lloyd McKenzie (Oct 12 2018 at 14:51):
@Bryn Rhodes do we have anything in this space yet? It seems like a cross between decision support and a "ConditionDefinition"
Bryn Rhodes (Oct 15 2018 at 16:01):
Looking at the documentation there, the criteria could certainly be captured with trigger definitions and libraries of criteria for what constitutes a particular episode. The question for me is what you want those definitions to actually do? Would they create the EpisodeOfCare that wrapped the relevant data elements? Or would it only be used as criteria for additional analytics and reporting downstream?
Mounika (Oct 29 2018 at 07:40):
Yes @Bryn Rhodes There are 98 Episode of care definitions.
For example, Episode of care of Asthma includes the following core components
Trigger codes
SubTypes
Relevant Diagnosis
Relevant Procedures
Relevant Pharmacy
SubType Groups.
Which resource is best to use to capture all these information?
Surya (Apr 05 2019 at 07:00):
Hi all, we want to create library entity for reference purpose ,can we use Fhir structures for that?
In that library we want Episode of care type,status,managing organization, triggering event(diagnosis | procedures ),code diagnosis,Potential avoidable complication.
we want to load this information in to Fhir server . This Episode of care is create an entity to what we are creating is library,the Fhir library resource is different ,so we can't combine both of them.
Suggest me to ,can we create a standard structure for this information ?
Lloyd McKenzie (Apr 05 2019 at 14:37):
It sounds like you're trying to define a "definition" for an EpisodeOfCare. Have you looked at PlanDefinition?
Surya (Apr 15 2019 at 11:17):
Thank you @Lloyd McKenzie I have gone through Plan definition resource ,but i am not sure by using which element we can capture all the information mentioned above.
Can anyone suggest me?
Jose Costa Teixeira (Apr 15 2019 at 11:23):
@Surya can you give an example?
for triggering event you have plandefinition.action.trigger .
for potential avoidable complication - could PlanDefinition.goal cover it? (@Bryn Rhodes )
Surya (Apr 15 2019 at 11:42):
Thank you @Jose Costa Teixeira
For example,we have a diagnosis AcuteMyocardialInfarction which will includes triggering codes,DRG codes,typical diagnosis codes,potentially avoidable complication codes ,procedure codes and cpt/hcpcs codes.How to capture all these codes?
Jose Costa Teixeira (Apr 15 2019 at 11:56):
oh then it starts looking like something other than a plandefinition
Bryn Rhodes (Apr 15 2019 at 14:26):
What you're describing sounds more complex than any single resource. PlanDefinition would be capable of structuring the information about what triggers the episode of care, and what the patterns are that should be used to capture the episode of care. I'm not clear on potentially avoidable complication, what would that look like in the actual episode of care?
Brian Postlethwaite (May 09 2019 at 14:21):
Anyone out there have a need to use an EpisodeOfCare compartment, or $everything operation, just as we have with Encounter to be able to get all the related material associated with an EpisodeOfCare
Grahame Grieve (May 09 2019 at 14:22):
I haven't seen the need.
Lloyd McKenzie (May 09 2019 at 18:13):
I long for when we do have the need - as I think it makes sense. But I don't think episodes are in wide use. It may be that GraphDefinition will eliminate the need, but I can see potential use for "give me the record for pregnancy x"
René Spronk (May 10 2019 at 07:03):
Personally I'm still baffled as to why we have the concept of Compartments at all. And yes, I've read its definition. But still I don't see the use case where this would be commonly used.
Re this discussion: GraphDefinition sounds to me like the thing one would like to use. It's either the client or the server who'll have to express "THIS (subset, graph) is what I'm looking for".
Brian Postlethwaite (May 10 2019 at 21:08):
For me it's the definition of what resource types to include in the $everything operation.
Last updated: Apr 12 2022 at 19:14 UTC
