Atomic Unit to capture the prognosis for a patient.

Prognosis

At any encounter with the patient, the professional offering care may re-assess the overarching life expectancy (prognosis) of the patient. This prognosis is immensely useful to urgent and emergency care in helping them to decide the best course of action for the patient. Across England, there is not yet a standard in place for commonly SNOMED-coding the prognosis. The ambition of all respondents was to standardise the SNOMED-coded part of the dataset to the four GSF values, however they all accepted that some localities were not using those values. Therefore, the prognosis (coded) data item allows for a wider selection of SNOMED codes to be transmitted. Additionally, the prognosis (textual) has been provided so that providers without any coding can still transmit the value in text.

The following FHIR profiles are used to form the prognosis Atomic Unit:

Prognosis data item mapping to FHIR profiles

The prognosis data items are fulfilled by elements within the FHIR resources listed below:

EOL Data Item FHIR resource element Mandatory/Required/Optional
Prognosis Coded EOL-ClinicalImpression-Prognosis-1.prognosisCodeableConcept Optional
Prognosis Textual EOL-Prognosis-ClinicalImpression-1.prognosisCodeableConcept.text Mandatory
Date of Prognosis EOL-Prognosis-ClinicalImpression-1.date Optional
Awareness of Prognosis EOL-Prognosis-ClinicalImpression-1-1.awarenessOfPrognosis (Extension) Optional
Professional Recording Prognosis EOL-Prognosis-ClinicalImpression-1.assessor Mandatory

EOL-Prognosis-ClinicalImpression-1.prognosisCodeableConcept (codeableConcept) Guidance

Where the sending system supports a terminology system:

  • The codeableConcept.coding element MUST be populated with:
    • system: identity of the terminology system (e.g. SNOMED-CT)
    • code: symbol in syntax defined by the system
    • display: representation defined by the system
  • the codeableConcept.text field MUST be populated with the display value from the codeableConcept.coding.display element e.g. ‘Asthma (disorder)’
  • the codeableConcept.text field MAY contain free text to capture more detail associated with the codeableConcept.coding.code e.g. ‘Patient uses blue inhaler to relieve symptoms’

Where the sending system does not support a terminology system:

  • the codeableConcept.text field MUST be populated with a text description of the concept as a human readable narrative e.g ‘Asthma’.
  • the codeableConcept.text field MAY contain free text to capture more detail associated with the concept e.g. ‘Patient uses blue inhaler to relieve symptoms’.

Prognosis Example XML