🚧

Roles

submitter

The observation object structure has a FHIR Resource Observation element structure

Patients have to be associated with the submitter otherwise observation will be rejected. See How to associate a patient with a submitter

Observation code matching

Each Observation (or inner component) has a code field which is an array ("codding") with different codes for the same observation. To be detected by the triggering system at least one of the codes (of the codding array) has to be matched with a code in the Triggers Configuration

Below is an example of trigger-matching observation

"code": {
  "coding": [
    {
      "system": "http://loinc.org",
      "code": "8462-4",							//<=this code in observation
      "display": "Diastolic blood pressure"
    },
    {
      "system": "another system",
      "code": "some-code",
    }
  ]
},

{
  "code" : "8462-4", //<= matched with this code in trigger
  "display" : "Diastolic blood pressure",   
  "logic" : { ">" : [ { "var" : "value" },100 ]
}

Observation component

Observation may have a composite structure i.e. component contains nested observations. When a new observation enters the system the sequence of analyses is the following:

1. The root element value analyzed (and alert triggered if needed)
2. Every child component is analyzed sequentially (and an alert is triggered for each if needed)