FHIR Chat · Encounter.hospitalization.reAdmission · implementers

Stream: implementers

Topic: Encounter.hospitalization.reAdmission


view this post on Zulip Joel Francis (Nov 08 2018 at 13:34):

Can I get some clarification on why Encounter.hospitalization.reAdmission is a CodeableConcept and not a boolean indicator? What conditions would warrant this and are there any other example concepts that one would use?

view this post on Zulip Lloyd McKenzie (Nov 08 2018 at 13:58):

@Brian Postlethwaite

view this post on Zulip Joel Francis (Nov 20 2018 at 16:32):

@Brian Postlethwaite

Any thoughts on this?????

view this post on Zulip Lloyd McKenzie (Nov 20 2018 at 18:24):

@Brian Postlethwaite

view this post on Zulip Brian Postlethwaite (Nov 23 2018 at 03:45):

@Cooper Thompson do you guys have an example set to use there?

view this post on Zulip Cooper Thompson (Nov 29 2018 at 21:45):

I'm investigating. Some spots we have readmission as a boolean. But I'm not sure about international realms. I'll circle back when I have more info. Probably next week due to some outages.

view this post on Zulip Joel Francis (Dec 03 2018 at 14:42):

I'm investigating. Some spots we have readmission as a boolean. But I'm not sure about international realms. I'll circle back when I have more info. Probably next week due to some outages.

Thanks @Cooper Thompson

view this post on Zulip Cooper Thompson (Dec 05 2018 at 19:14):

Ok, so I learned more about readmissions than I really ever wanted to. Some points to consider:

  • Generally, in the US, "readmission" means "unplanned" readmission. Just because it is the second admission in a given period does not mean it is a "readmission". E.g. if you have a plastic surgery planned months in advance as your second admission in a given time period, it would not be considered a "readmission".
  • Determining whether an encounter is considered a readmission generally involves running some sort of model. In the US, CMS has a good set of models that are widely accepted (but there are some dissenting opinions).
  • Knowing if an encounter is a readmission is tricky when the admissions span different healthcare systems. In the US, readmission information is often calculated well after the fact based on claims data that CMS receives from potentially multiple healthcare systems. At the time of an encounter, it may not be possible to know if it is a "readmission", if the patient was recently admitted for the same condition at a different hospital.
  • A patient's conditions and other risk factors are key data points for calculating if something is a readmission.

In the end, we do represent readmission as a boolean. However it can be possible for different authorities to disagree on what is considered a readmission. So we might consider including the authority that is categorizing the admission as a readmission, and potentially an indicator of what model was used in the determination. Those may also be good candidates for extensions. But we might need to consider making the property 0..* to account for different authorities classifying an admission differently.

view this post on Zulip Lloyd McKenzie (Dec 11 2018 at 01:42):

It sounds like an Observation to me. It's a point-in-time assertion made based on a set of facts following a particular set of rules. Different assertions about the same two encounters might be made by different authors because they're using different rules or using different sets of inputs. Observation would let you tie those things together. So you could say "this is a re-admission from payer 1's perspective, but not from payer 2's perspective"


Last updated: Apr 12 2022 at 19:14 UTC