Stream: implementers
Topic: Slicing references to profiles
Ludvig Eek Hofmann (Mar 26 2020 at 07:35):
We are have created a profile for triage using the resource ClinicalImpression. The triage includes a reason for visit, triage level and several vital signs. In the profile we therefore want to use references to several profiles on the resource Observation. One for each of the vital signs.
In the ClinicalImpression profile we wanted to slice on the element ClinicalImpression.Investigation using the discriminator for profile. Meaning that if we refer to a profile for e.g. blood pressure the fixed Snomed CT code for blood pressure should be used. The problem is that “this provides the most power, since the full range of profiling capabilities are available, but it is also the hardest to implement, and requires the most processing (>1000-fold compared to the others)” it should only be used if there is no other option.
How should we slice the ClinicalImpression.investigation in the best way to. We want to minimize the logic required for the external system. Do you think slicing it on the code and then use a fixed value on the profile reference? Is that possible?
Lloyd McKenzie (Mar 26 2020 at 14:18):
When dealing with reference, slicing by type and then by code is certainly more efficient than slicing by profile
Last updated: Apr 12 2022 at 19:14 UTC
