Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
US Core (FHIR)
-
6.0.0-ballot [deprecated]
-
Cross-Group Projects
-
STU
-
US Core Observation Clinical Result Profile
US Core Observation Screening Assessment Profile
US Core Simple Observation Profile -
-
Eric Haas / Yunwei Wang : 13-0-0
-
Clarification
-
Compatible, substantive
Description
Background:
"US Core Observation Screening Assessment Profile" has Observation.category element binds to these codes:
- http://terminology.hl7.org/CodeSystem/observation-category|survey
- http://hl7.org/fhir/us/core/CodeSystem/us-core-category|sdoh
- http://hl7.org/fhir/us/core/CodeSystem/us-core-category|functional-status
- http://hl7.org/fhir/us/core/CodeSystem/us-core-category|disability-status
- http://hl7.org/fhir/us/core/CodeSystem/us-core-category|cognitive-status
"US Core Simple Observation Profile" has Obervation.category element binds to value set "US Core Simple Observation Category" which also contains these four codes
"US Core Observation Clinical Result Profile" has Observation.category element binds to value set "ObservationCategoryCodes" which also contains the same code survey
Question:
That brings a question that when client searches with Observation?category=survey, what profile(s) do the returned resources conform to? Is it "US Core Observation Screening Assessment Profile", "US Core Observation Clinical Result Profile", "US Core Simple Observation Profile", or all of them?
The question can also be expressed as, according to US Core 6, all resources conforming to "US Core Observation Screening Assessment Profile" SHALL have Observation.category = survey. Is it also true that all resources having Observation.category = survey SHALL conform to "US Core Observation Screening Assessment Profile".
This is critical issue for Bulk data interactions because Bulk data export are groups by resource types not profiles. When an export requester get an Observation NDJSON files, it is very tricky to figure out the profiles for each Observation resources.
Recommendation
US Core provides a clear instruction on how a resource maps to one or some target profiles.
Attachments
Issue Links
- is voted on by
-
BALLOT-46152 Negative - Yunwei Wang : 2023-Jan-FHIR US CORE R5.1.0 STU
- Withdrawn
- relates to
-
FHIR-40034 Rename US Core Observation Category
- Published
-
FHIR-39940 Change the title and/or description of the Simple Observation Profile
- Published
-
FHIR-40087 Consider managing resource “domain” category slices with a common pattern
- Published