Composition

VKP uses the standard Composition resource defined by HL7. There is no VKP specific profile for the Composition resource.

The information model for the Composition sent separately or in the Message Bundle is used to document how the response centre resolved/reacted to an actual event. The information is sent to VKP as a Composition, and VKP records that information in the EPR as a Consult Note.

A Composition is also used to represent information returned from the EPR.

Use cases

Composition is used in the following use cases:

  1. Write a journal post related to actions taken to a resolved alarm
  2. Get journal document related to planned measures for a patient

Composition can also be used in a Bundle, to represent textual information with an Encounter (or a MedicationDispense). See those profiles for related use cases.

Write a journal post related to actions taken to a resolved alarm

Response senter do a POST Composition to store a a journal post related to actions taken to a resolved alarm in the EHR.

Usage of profile attributes

The Composition profile contains two main elements; events and sections.

Events contain structured, timestamped information describing important events.

Sections contain textual descriptions and are used for additional, and normaly manually registered, information.

The following table summarizes the Composition fields that are important for use in the VKP APIs when sending information to VKP. For complete documentation, see http://www.hl7.org/fhir/STU3/composition.html.

Field Description
Status Fixed value: 'final'. CompositionStatus according to http://hl7.org/fhir/ValueSet/composition-status
type Fixed value: LOINC 34133-9, "Summarization of episode note“
subject Reference to the patient this composition is about: Birth number and name.
class Fixed value: 1, “respons_notat”
date Date/timestamp when the composition was submitted.
author The health care professional that handled the case. Can be a response center operator or a municipal employee. Birth number (or other unique ID from the system) and name.
title Fixed value: "Journalnotat for respons på hendelse“
event List of structured, timestamped information describing the main events/steps of the handling of the case
event.code Code describing the event type according to event-codes
event.period.start Timestamp of the event
section List of textual descriptions.
section.title Title descring the type of this section. Titles are standardized – see table below.
section.text.status Fixed value: "additional"
section.text.div HTML content

Section titles

The following section titles are pre-defined. Signature and alarm information are required, the rest are optional.

Title Description (Norwegian)
Alarm information Hva slags enhet/utstyr som var opphav til hendelsen
Reason Årsak, den som blir stående når behandling er avsluttet
Reason updates Historikk på årsaksoppdateringer, endret til + bruker-ID
Response summary Tiltak, det som blir stående når behandling er avsluttet
Response summary updates Historikk på tiltaksoppdateringer (som for årsak)
Response elaboration Kommentar, det som blir stående når behandling er avsluttet
Response elaboration updates Historikk på oppdatering av kommentar (som for årsak / tiltak)
Response service calls Samtaler startet fra responsløsningen
Emergency action Utrykning / overføring til hjemmetjenesten: Ansvar overført til <navn på enhet>, + eventuell informasjon om avvisninger
Signature <Navn + (bruker-ID)> for den operatøren som avsluttet / kvitterte ut hendelsen
Other operators <Tidspunkt + bruker-ID> for andre involverte operatører enn den som avsluttet

Response senter do GET Composition to receive information related to planned measures for a patient.

Search parameters and return values

For the GET command the server is expected to return a set of one or more Composition resources as a Bundle. If an error occurs an OperationOutcome resource should be returned. For the WRITE command the server is expected to return an OperationOutcome resource.

Changes from v05 -> v06

XPath v06 v05
/subject/identifier/system urn:oid:2.16.578.1.12.4.1.4.1 http://ehelse.no/fhir/identifiertypes/FNR
/author/identifier/system urn:oid:2.16.578.1.12.4.1.4.1 http://ehelse.no/fhir/identifiertypes/FNR
/author/identifier/system urn:oid:2.16.578.1.12.4.1.4.4 http://ehelse.no/fhir/identifiertypes/HPR

Examples

Example Information
Example Bundle with Composition and Encounter Example (JSON) of a Bundle with Composition and Encounter.
Example Composition - Tiltaksplan Example (JSON) of a Bundle with Composition (Tiltaksplan).
Example Composition-Bundle-Aktivering av varsler Example (JSON) of a Bundle with Composition events.