When expressions are used to record clinical data, it is important to establish effective ways of communicating these expressions with other systems.

The main options for sharing postcoordinated expressions are:


{
  "resourceType": "Condition",
  "id": "f205",
  "text": {
    "status": "generated",
    "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">...</div>"
  },
  "clinicalStatus": {},
  "verificationStatus": {},
  "code": {
    "coding": [
       {
        "system": "http://snomed.info/sct",
        "code": "301354004 |Pain of ear| : 272741003 |Laterality| = 7771000 |Left|",
        "display": "Left ear pain"
      },
      {
        "system": "http://snomed.info/sct",
        "code": "301354004 |Pain of ear|",
        "display": "Pain of ear"
      }
    ]
  },
  "subject": {
    "reference": "Patient/f201",
    "display": "PP"
  },
  "recordedDate": "2013-04-04",
  "asserter": {
    "reference": "Practitioner/f201"
  }
}



Enabling expressions to be included in communication messages requires:

  • 5.2.7 Lookup Expression. This will be used to get either the CTU form of the expression or the expression identifier to be included as the code for the coded data element in the message
  • 5.2.9 Get Display Term. This is required in cases where a single display term is required for the expression, and this approach is acceptable in the given setting.

Note that additional terminology services will be required to decompose expressions to enable the separation of values into specific fields of the message structure.