Details
-
Change Request
-
Resolution: Not Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R5
-
Orders & Observations
-
Observation
-
-
Marti Velezis / Dan Rutz : 18 - 0 - 0
-
Clarification
-
Non-substantive
-
R6
Description
FHIR#17901 was snuck in before Observation, moving EpisodeOfCare to an extension, and renaming Observation.context to Observation.encounter.
That tracker (or related set of trackers) spawned FHIR#19513 for PA to update some of our resources (specifically, ChargeItem) to align with the pattern in Observation.
We (PA) are going to reject that proposal, and keep ChargeItem.context (Encounter | EpisodeOfCare). However, when looking at the issue history, the change in FHIR#17901 (also discussed in this chat.fhir topic) seemed odd.
The 2021 Argo Write project is working on an IG to support patients writing data to EHRs. This would be items like steps, or vitals collected at home. This data fits directly into Observations that have no encounter, but may have an EpisodeOfCare.
We think O&O should revisit the Observation.encounter/context change. I get that Observation is normative, but as I've said on chat.fhir, at some point we (FHIR) will need to figure out how to make normative updates...
Attachments
Issue Links
- relates to
-
FHIR-17794 change .context back to.encounter
- Duplicate
-
FHIR-19513 Substantive workflow changes for PA resources
- Published
-
FHIR-17901 Revamp "context" element to be a reference to Encounter and an extension for EpisodeOfCare
- Published
-
FHIR-23029 CareTeam.encounter should support cardinality 0..*
- Published
-
FHIR-42761 Revamp "encounter" element to be a reference to Encounter and EpisodeOfCare
- Resolved - No Change