Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

The following Library resources and contained rules constitute examples that show various aspects of rules and intended use. They do not constitute properly tested or production-ready rules, even if they might come close.

Automated Processing Type Library Resource Examples

Common to the Library resource examples is that they have a Library.type set to automated-processing.

In the example descriptions, Coding values have been reduced to the Coding.code element solely for brevity and where there is little if any ambiguity when the reader checks the ValueSet binding of the corresponding element in the profile. As apparent in the actual rule code listings here (which

...

are not normative), Coding values must be specified properly and in accordance with the eHealth Implementation Guide’s General Guidance.

The Fallback Library

The Fallback Library is intended as a rule that ensures creation of a Task that draws attention to a measurement needing evaluation. This in case no other automated processing type library has been set up for a given ProcedureRequest through its ActivityDefinition.

The Library has:

  • .type set to automated-processing

  • .parameter

    • .use set to in for input

    • .type set to Observation

The Library rule sets up instructions that causes production of a:

a Task with:

...

.category set to MeasurementForAssessment (a Coding signifying a measurement should be assessed/evaluated)

...

.priority set to routine

...

.description set to “Måling til vurdering” which is Danish for measurement to be assessed

...

Automated Processing Type Library Resource Examples

Common to automated processing type Library resources is that they have a Library.type set to automated-processing and specify no output type parameters in Library.parameter. In reality, evaluation of the Library causes return of a GuidanceResponse containing a AutomatedProcessingDTO structure with instructions, but this need not be declared.

Except for the Fallback Library, evaluation of an automated processing type Library requires that a measurement has been submitted and that the ServiceRequest refers to an ActivityDefinition which refers to the Library, that is, the Library must be used in a CarePlan complex associated with the Patient for which a measurement is submitted.

Library Triaging Against Reference Ranges

This Library is intended for use with an ActivityDefinition which specifies submitting of an Observation where the submitted Observation.value is to be compared against the reference range(s) defined in the ProcedureRequest ServiceRequest associated with the ActivityDefinition.

...

  • .type set to automated-processing

  • .parameter

    • .use set to in for input

    • .type set to Observation

As it is an automated-processing type, no output type parameters are specified. In reality, evaluation of the Library causes return of a GuidanceResponse containing a AutomatedProcessingDTO structure with instructions, but this need not be declared.

The Library rule sets up instructions that causes production of aThe Library rule sets up instructions that causes production of a:

  • a Task with:

    • .category set to MeasurementForAssessment (a Coding signifying a measurement should be assessed/evaluated)

    • .priority set to:

      • routine when the Observation.value is within reference range

      • urgent when the Observation.value is outside a “Yellow Alarm” type reference range (if defined) but within a “Red Alarm” type reference range (if defined)

      • asap when the Observation.value is outside the “Red Alarm” type reference range (if defined)

    • .description set to “Måling til vurdering” which is Danish for measurement to be assessed

    • further elements set as described in Output from automated processing

  • a ClinicalImpression with:

    • .code set to TriagingResult

    • .finding.itemCodeableConcept.Coding set to:

      • a Coding signifying a finding that a measurement is within reference range when that is the case

      • a Coding signifying a finding that a measurement is above reference range when that is the case - this whether above Red Alarm or above Yellow Alarm (but within Red Alarm)

      • a Coding signifying a finding that a measurement is below reference range when that is the case - this whether below Red Alarm or below Yellow Alarm (but within Red Alarm)

    • .description set to “Automatisk processering grundet måling modtaget” which is Danish for automated processing due to submitted measurement

    • further elements set as described in Output from automated processing

  • a Communication (of ehealth-message profile) provided that the Task.priority is not routine (that is, when the measurement is outside any reference range) with:

    • .ehealth-restriction-category that restricts access for Practitioners to those monitoring measurements

    • .reasonCode set to MeasurementForAssessment

    • .payload.content set to “Måling til vurdering” which is Danish for measurement to be assessed (in the Default message)

    • further elements set as described in Output from automated processing

...

Expand
titleCAT Score Rule Content
Code Block
package rules
import org.hl7.fhir.dstu3.model.Quantityimport
// Further imports omitted for brevity

global com.systematic.ehealth.automatedprocessing.AutomatedProcessingDTO ruleResult

function ObservationDTO createObservation(int sum) {
   QuantityDTO quantityDTO = new QuantityDTO((double)sum, "score");
   ObservationDTO observationDTO = new ObservationDTO();
   observationDTO.setStatus("final");
   observationDTO.setCode(new CodingDTO("urn:oid:1.2.208.184.100.8", "MCS88137", "CAT score;Pt"));
   observationDTO.setValueQuantity(quantityDTO);
   return observationDTO;
}

function ClinicalImpressionDTO createClinicalImpression(ObservationDTO finding) {
   String clinicalImpressionDescription = "Automatisk processering grundet måling modtaget";
   CodingDTO clinicalImpressionCode = new CodingDTO("http://ehealth.sundhed.dk/cs/clinicalimpression-codes", "TriagingResult", "Result of triaging");
   return new ClinicalImpressionDTO(clinicalImpressionCode, clinicalImpressionDescription, List.of(), List.of(finding));
}

function TaskDTO createTask(String taskPriority) {
   List<CommunicationDTO> communications = new ArrayList<>();
   String description = "Måling til vurdering";
   CodingDTO taskCategory = new CodingDTO("http://ehealth.sundhed.dk/cs/task-category", "MeasurementForAssessment", "Need assessment of measurement");
   CodingDTO taskRestrictionCategory = new CodingDTO("http://ehealth.sundhed.dk/cs/restriction-category", "measurement-monitoring", "Monitoring of measurement(s)");
   return new TaskDTO(taskCategory, description, taskPriority, List.of(taskRestrictionCategory), communications);
}

rule "CATScoreRule"
dialect "java"

when
   col : Collection()
   listQrs : ArrayList() from collect (EHealthQuestionnaireResponse() from col)
   qr : EHealthQuestionnaireResponse() from listQrs.get(0)
then
   int sum = qr.getItem().stream()
     .map(QuestionnaireResponseItemComponent::getAnswerFirstRep)
     .filter(QuestionnaireResponseItemAnswerComponent::hasValueIntegerType)
     .map(QuestionnaireResponseItemAnswerComponent::getValueIntegerType)
     .map(IntegerType::getValue)
     .reduce(0, Integer::sum);

   ObservationDTO observation = createObservation(sum);
   
   ruleResult.setClinicalImpressions(List.of(createClinicalImpression(observation)));
   ruleResult.setTasks(List.of(createTask(sum < 15 ? "routine" : "urgent")));
end;

Library Activating a Self-Treatment ProcedureRequest

An example use for this Library is to trigger activation of one or more ProcedureRequest Although the example here uses Questionnaire answers of integer type, the principle in the Library can easily be adjusted to processing of coded answers as long as they each have an integer value correspondence.

Library Activating a Self-Treatment ServiceRequest

An example use for this Library is to trigger activation of one or more ServiceRequest of self-treatment type based on answers (a QuestionnaireResponse) to a Questionnaire or, alternatively, computed from a submitted Observation. In the following, it is assumed that triggering is based on a QuestionnaireResponse.

In the initial state, the CarePlan would contain:

  • a number of ProcedureRequestServiceRequest, say, specifying measuring and questionnaire answering activities (this is typical content but irrelevant for activation of the self-treatment activity).

  • an active ProcedureRequestServiceRequest, here denoted the trigger ProcedureRequestServiceRequest, specifying answering of the Questionnaire that triggers the self-treatment activity

  • an inactive (through a ProcedureRequestServiceRequest.status set to suspended) self-treatment type ProcedureRequestServiceRequest. This could specify an activity to perform a weight measurement or answering of a self-treatment related Questionnaire.

The trigger ProcedureRequest ServiceRequest references an ActivityDefinition which references the Library described below.

...

The Library rule sets examines the answers of the QuestionnaireResponse and, in case triggering is needed, sets up the instruction through the line ruleResult.setActivateSelfTreatment(true);

Expand
titleSelf-Treatment ProcedureRequest ServiceRequest Activation Rule Content
Code Block
package rules
import org.hl7.fhir.dstu3.model.QuestionnaireResponse
// Further imports omitted for brevity

global com.systematic.ehealth.automatedprocessing.AutomatedProcessingDTO ruleResult

rule "SelfTreatmentProcedureRequestActivationRuleSelfTreatmentServiceRequestActivationRule"

dialect "java"

when
   $questionnaireResponses : Collection()
   $listQrs : ArrayList() from collect (QuestionnaireResponse() from $questionnaireResponses)
then
   QuestionnaireResponse qr = (QuestionnaireResponse)$listQrs.get(0);
   boolean activate = false;
   
   // QuestionnaireResponse examined (omitted), activate set to true when needed
   
   ruleResult.setActivateSelfTreatment(activate);
end

The automated processing reaction to a true parameter passed to setActivateSelfTreatment is described in Activation of suspended Self-treatment type ProcedureRequest.

Calculation Type Library Resource Examples

Library for Calculating Situation Quality

...

);
end

The automated processing reaction to a true parameter passed to setActivateSelfTreatment is described in Activation of suspended Self-treatment type ServiceRequest.

Calculation Type Library Resource Examples

A calculation type Library resource has a Library.type set to logic-library and its evaluation requires invocation of its evaluate operation with input parameters as specified in the Library.

Library for Calculating Situation Quality

This Library and its rule is intended to qualify a measurement, typically submitted as an Observation or Media. Typically the associated Questionnaire poses questions relevant to the quality of that particular measurement, for instance whether a finger is warm (could be relevant for Pulse Oximeter measurement of oxygen saturation at index finger) or whether the patient is sitting or lying down. Prerequisite to submitting the Observation, the QuestionnaireResponse for the said Questionnaire would be passed as parameter to the evaluate operation on the Library, returning one or more Coding in the SituationQuality. The returned Coding(s) would then be entered in Observation.ehealth-quality.

The Library has:

  • .type set to logic-library

  • .parameter[0]

    • .use set to in for input

    • .type set to QuestionnaireResponse

  • .parameter[1]

    • .use set to out for output

    • .type set to CodeableConcept

The Library rule sets examines the answers of the QuestionnaireResponse and determines the corresponding SituationQuality Coding(s).

Expand
titleSituation Quality Calculation Rule Content
Code Block
package rules
import org.hl7.fhir.dstu3.model.QuestionnaireResponse
// Further imports omitted for brevity

global org.hl7.fhir.dstu3.model.CodeableConcept ruleResult

rule "SituationQualityCalculationRule"
dialect "java"

when
   $questionnaireResponses : Collection()
   $listQrs : ArrayList() from collect (QuestionnaireResponse() from $questionnaireResponses)

then

   QuestionnaireResponse qr = (QuestionnaireResponse)$listQrs.get(0);
   Coding coding = new Coding();

   // Examination of QuestionnaireResponse determines the Coding(s) to return
      coding.setCode("SQ2");
      coding.setSystem("http://ehealth.sundhed.dk/cs/situation-quality");
      coding.setDisplay("Situation Quality 2");
   }
   ruleResult.addCoding(coding);

end;

Library for Calculating Usage Quality

The Library and rule for calculating Usage Quality is very similar to the Library for Calculating Situation Quality and is also intended to qualify a measurement, typically submitted as an Observation or Media. The difference is that the Questionnaire, which is the typical way to establish usage quality, poses questions relevant to the quality of how the involved Device (if any) was operated, for instance has the instructions for device use been followed.

Prerequisite to submitting the Observation, the QuestionnaireResponse for the said Questionnaire would be passed as parameter to the evaluate operation on the Library, returning one or more Coding for UsageQuality. The returned Coding(s) would then be carried to Observation.ehealth-quality.

The Library type, input and output are identical to that of Library for Calculating Situation Quality, and the rule differs in that the resulting Coding specifies UsageQuality.