...
The Fallback Library contains a rule that ensures creation of a Task that draws attention to a measurement needing evaluation. It is intended for implicit use in case no other automated processing type Library has been set up for a given ProcedureRequest ServiceRequest through its ActivityDefinition.
...
This Library contains a generic rule that performs assessment of an Observation based on absolute reference range(s) automatically copied from a ProcedureRequest ServiceRequest referencing an ActivityDefinition that references the Library. The rule in this Library is automatically performed as a reaction to submitting of the Observation. This Library can be referenced from an ActivityDefinition along with other Library, even the Relative Reference Ranges Library described below.
...
A ClinicalImpresssion:
.finding
for each.component
in the observation (e.g. systolic and diastolic blood pressure) or a single finding if the observation does not contain components.Each finding for observation will have one of the following alert levels:
http://snomed.info/sct, 442082004, fund ved måling inden for referenceinterval (green)
http://snomed.info/sct, 442096005, fund ved måling uden for referenceinterval (red, yellow)
If the finding is for a component, then it will contain an observation code identifying the component (e.g. systolic blood pressure)
A Task related to the ClinicalImpression with priority based on the highest alert level found:
asap
if .
.finding
for the overall assessment which is eithergreen
,yellow
orred
based on the worst severity from components or a single observation, seegreen
,yellow
andred
in .https://ehealth.sundhed.dk/fhir/ValueSet-ehealth-clinicalimpression-finding-codes.html .A Task related to the ClinicalImpression with
priority
based on the highest alert level found:asap
if any values are found in “red alert” reference rangesurgent
if any values are found in “yellow alert” reference ranges (and no “red alert” found)routine
if no red or yellow alerts are found
...
The rule processes absolute reference ranges only, that is, Observation.referenceRange.type
where the Coding has:
system
:urn:oid:1.2.208.184.100.1
code
:RAL
orGAL
, for red alarm absolute reference range and yellow alarm absolute reference range, respectively.
...
The rule accepts observation values and reference ranges without units. However if both have a unit specified, they must match.
Assessment of Relative Reference Ranges Library and Rule
This Library is similar to the Absolute Reference Range library (see above) in some aspects: Input and output are identical. The difference is the the type of reference ranges that the rule handles. Absolute and relative reference range libraries can co-exist and can both process the same Observation. They will each handle their corresponding type of reference ranges associated with the Observation.
The rule processes relative reference ranges only, that is, Observation.referenceRange.type where the Coding has:
...
Error handling for different situations which result in the rule setting up instructions for creation of one or two Task:
Situation | Generic Task | Possible Specific Task (Stating what was wrong) |
---|---|---|
No absolute reference range found | Task (Stating that measurement needs manual assessment):
|
...
code
: RELRAL
or RELGAL
, for red alarm relative reference range and yellow alarm relative reference range, respectively.
A vital difference from the rule in the Absolute Reference Range Library is that Relative Reference Range Library rule must have a reference base to compare against.
A relative reference range can be stated:
in same unit as the Observation
as a percentage or, in case the Observation is already expressed with unit percentage (as is the case for oxygen saturation, for instance), as a percentage point.
...
Example relative reference range as -5 percentage point with reference base 90% for oxygen saturation measurement
The oxygen saturation measurement unit is expressed as percent (system=http://unitsofmeasure.org
, code=%
), the reference base likewise and in this case with a value of 90.
A red alarm relative reference range given as -5 percentage point would be given by a SimpleQuantity for the reference range’s low element with:
...
value=-5
...
unit=percentage point
| No additional task. |
Unit mismatch between reference range and observation value | Task (Stating that measurement needs manual assessment as auto processing failed):
|
...
code=percentagepoint
...
| Task:
| |
Missing observation value | Task (Stating that measurement needs manual assessment as auto processing failed):
| Task:
|
Assessment of Relative Reference Ranges Library and Rule
This Library is similar to the Absolute Reference Range library (see above) in some aspects: Input and output are identical. The difference is the the type of reference ranges that the rule handles. Absolute and relative reference range libraries can co-exist and can both process the same Observation. They will each handle their corresponding type of reference ranges associated with the Observation.
The rule processes relative reference ranges only, that is, Observation.referenceRange.type where the Coding has:
system
:http://ehealth.sundhed.dk/cs/reference-range-type
code
:RELRAL
orRELGAL
, for red alarm relative reference range and yellow alarm relative reference range, respectively.
A vital difference from the rule in the Absolute Reference Range Library is that Relative Reference Range Library rule must have a reference base to compare against.
A relative reference range can be stated:
in same unit as the Observation
as a percentage or, in case the Observation is already expressed with unit percentage (as is the case for oxygen saturation, for instance), as a percentage point.
Info |
---|
Example relative reference range as -5 percentage point with reference base 90% for oxygen saturation measurement The oxygen saturation measurement unit is expressed as percent ( A red alarm relative reference range given as -5 percentage point would be given by a SimpleQuantity for the reference range’s low element with:
Thus, the rule would treat an Observation with value 85% as a red alarm case for this relative reference range and current choice of reference base with value 90%. |
The rule handles different situations which result in the rule setting up instructions for creation of one or two Task:
Situation | Generic Task | Possible Specific Task (Stating what was wrong) |
---|---|---|
Neither reference base nor relative reference range(s) found | Task:
| No additional task. |
No reference base found | Task:
| |
No relative reference range found | Task:
|
Library for Assessment of Questionnaire Response
This Library contains a generic rule that performs assessment of a QuestionnaireResponse in relation to any answer significances defined in the corresponding Questionnaire.
During processing of the rule, each answer significance defined in the Questionnaire (see https://ehealth.sundhed.dk/fhir/StructureDefinition-ehealth-questionnaire.html#answer-significance ) on questions and their linked answers in the QuestionnaireResponse are traversed and checked whether the condition(s) of the answer significance is met by the linked answer. When this is the case, a finding basis is added to internal bookkeeping. Ultimately, the list of finding basis determines the created ClinicalImpression finding and the priority of the created task:
In case the list of finding basis contains at least one red question/answer pair, the priority is set to
asap
In case the list of finding basis contains at least one yellow question/answer pair and no red question/answer pair , the priority is set to
urgent
Otherwise, the priority is set to
routine
The Library has:
.type
set toautomated-processing
.parameter
.use
set toin
for input.type
set toQuestionnaireResponse
.parameter
.use
set toin
for input.type
set toQuestionnaire
.parameter
.use
set toin
for input.type
set toServiceRequest
The Library rule sets up instructions that causes production of:
A ClinicalImpresssion:
.finding
as follows:If the triggered red set is not empty, a
finding.item
with a Coding:system
=http://ehealth.sundhed.dk/cs/clinicalimpression-finding-codes
code
=red
display
=Red overall assessment
If the triggered yellow set is not empty, a
finding.item
with a Coding:system
=http://ehealth.sundhed.dk/cs/clinicalimpression-finding-codes
code
=yellow
display
=yellow overall assessment
If both triggered sets are empty, a
finding.item
with a Coding:system
=http://ehealth.sundhed.dk/cs/clinicalimpression-finding-codes
code
=green
display
=Green overall assessment
If the Questionnaire does contain answer significance definitions but none have been triggered, a
finding.item
with a Coding:system
=http://ehealth.sundhed.dk/cs/clinicalimpression-finding-codes
code
=no-effective-answer-significance
display
=Ingen triageringsindikator for spørgsmål/svar-kombination har fundet anvendelse
If the Questionnaire does not contain answer significance definitions, a
finding.item
with a Coding:system
=http://ehealth.sundhed.dk/cs/clinicalimpression-finding-codes
code
=no-answer-significance-defined
display
=Ingen triageringsindikator defineret i spørgeskemaet
list of
.ehealth-questionnaireresponse-finding-basis
for each basis for the overall ClinicalImpression as follows:linkId
set to linkId for the Questionnaire item/QuestionnaireResponse item pair which triggered the finding basisvalue
set to value of the answer which triggered the finding basisfinding
set togreen-question-answer
,yellow-question-answer
orred-question-answer
fromhttp://ehealth.sundhed.dk/vs/clinicalimpression-finding-codes
based onsignifiance
on triggeredehealth-questionnaire-answerSignificance
ehealth-questionnaire-answerSignificance
is the triggeredanswerSignificance
which is gathered from Questionnaire item
A Task related to the ClinicalImpression with:
priority
set to the priority value determined above.
A difference between the finding in finding.item.code
and the finding basis in ehealth-questionnaire-finding-basis
is that the former is a conclusion or summary while the latter provides the details that led to the conclusion. In ehealth-questionnaire-finding-basis
there may be multiple entries for the same question-answer pair and those entries may or may not have the same significance (color). That depends on the how the answer (or lack of answer) fits with answer significance definitions in the Questionnaire.
Assessment of TeleCare Nord COPD Questionnaire
...
.type
set toautomated-processing
.parameter
.use
set toin
for input.type
set toQuestionnaireResponse
.parameter
.use
set toin
for input.type
set toQuestionnaire
.parameter
.use
set toin
for input.type
set toProcedureRequest
ServiceRequest
The Library rule sets up instructions that causes production of:
...
.type
set tologic-library
.parameter[0]
.use
set toout
for output.type
set toCoding
.parameter[1]
.use
set toin
for input.type
set toObservation
.parameter[2]
.use set to
in
for input.type
set toProcedureRequest
ServiceRequest
The input Observation must have
.code
: Coding for height (code=NPU03794, system=urn:oid:1.2.208.176.2.1)effectiveDateTime
basedOn
referencing a ProcedureRequest ServiceRequest
It is not necessary to provide the ProcedureRequest ServiceRequest as input. The Libary$evaluate operation will retrieve it by resolving the basedOn
reference in the Observation.
Output will be a code from the http://hl7.org/fhir/v3/ObservationInterpretation CodeSystem:
Output Coding | Evaluation |
---|---|
code=IND, system=http://hl7.org/fhir/v3/ObservationInterpretation, display=Indeterminate | The referenced |
ServiceRequest does not contain | |
code=N, system=http://hl7.org/fhir/v3/ObservationInterpretation, display=Normal | The height Observation has not exceeded the max age specified in |
ServiceRequest. | |
code=L, system=http://hl7.org/fhir/v3/ObservationInterpretation, display=Low | The height Observation has exceeded the max age specified in |
ServiceRequest. |
Library for Calculating Body Mass Index
...
.type
set tologic-library
.parameter[0]
.use set to out for output
.type set to Quantity
.parameter[1]
.use
set toin
for input.type
set toObservation
.parameter[2]
.use set to
in
for input.type
set toProcedureRequest
ServiceRequest
The library expects two observations as input:
The first Observation must be a weight observation (code=NPU03804, system=urn:oid:1.2.208.176.2.1)
The second Observation must be height observation (code=NPU03794, system=urn:oid:1.2.208.176.2.1)
It is not necessary to provide the ProcedureRequest ServiceRequest as input. The Libary$evaluate operation will retrieve it by resolving the basedOn
reference in the weight Observation.
...