Finnish PHR Vital Signs Base profile
The Finnish PHR Vital Signs Base Profile UPDATED constrains and extends FHIR® Vital Signs STU3 profile for FHIR® Observation. This Finnish PHR profile defines profiled elements used in all other Finnish PHR profiles derived from this profile. This base profile can not be used as a resource instance, it is a base definition (abstract) for other Finnish PHR vital signs profiles.
A full list of the extensions, constraints and a structured definition of this profile can be found in Simplifier. There are also different views of the profile (details, mappings, table, XML, JSON).
Mandatory elements for all Finnish PHR vital signs
| Content | Name in structure | Description / Type of information |
|---|---|---|
| Language | language | Language used in the observation stored in Kanta PHR. Language SHALL be chosen from the FHIR languages ValueSet. |
| Narrative | text | A text summary of the observation. SHALL include all content for a human to understand the essential clinical and business information of the observation.
A narrative guide will be provided for each of the derived profiles. |
| Unique identifier | identifier | At least one globally unique identifier has to be provided for the observation, in addition other identifiers may be given as well.
This identifier may be used to uniquely identify the observation if the application doesn't receive an id for the observation provided by Kanta PHR. |
| Status | status | The status of the observation. Only completed observations are stored in Kanta PHR, thus the status SHALL always be 'final' (from FHIR Observation Status ValueSet). |
| Category of the observation | category | Indicates to what category the observation belongs to. All vital signs SHALL have the category 'vital-signs' (from FHIR Observation Category ValueSet). |
| Code of the observation | code | Determines what the observation is (ie. a measurement of blood pressure, blood glucose, height, etc.). Codes are allowed only from the LOINC code system, and all the allowed codes can be found in Finnish PHR Vital Signs ValueSet.
The exaxt code(s) to be used will be determined in the derived profile for each different kind of an observation. |
| Subject of the observation | subject | Who this observation is about. The reference SHALL be to a Patient resource stored in Kanta PHR (that conforms to the Finnish PHR Patient profile). |
| Time for the observation | effectiveDateTime | Clinically relevant time for the observation.
The precision of time will vary depending on what kind of an observation is in question. For example in some cases, the time for the observation may include the exact date and time when the observation was made. In other cases, only the date will be stored. |
| Storing date | issued | The date and time the observation was stored in Kanta PHR. |
| Who is responsible for the observation | performer | This may be the same as the subject, or this may be another person for example when someone is using Kanta PHR on behalf of the subject. The reference SHALL be to a Patient resource stored in Kanta PHR (that conforms to the Finnish PHR Patient profile). |
Optional elements for all Finnish PHR vital signs
| Content | Name in structure | Description / Type of information |
|---|---|---|
| Actual result | value[x]/ component |
Includes the observation result, for example in a height observation the actual measured height, or in a blood glucose observation the actual measured blood glucose level. In some observations, the actual result has multiple components (for example a blood pressure measurement has a systolic and a diastolic value). In these kind of observations, the actual result is stored under the component structure. Either the actual result or a reason for why the (structured) result is missing (see below) SHALL be provided. The unit of measurement that SHALL be used will be determined in the derived profiles for each different kind of an observation. |
| A reason why the (structured) result is missing | dataAbsentReason | Indicates the reason why the (structured) result is missing. The code for the reason SHALL be from FHIR Observation Value Absent Reason ValueSet.
This might be used for example when a device or an application is for some reason unable to provide the result in a structured form and has to store it only in the Narrative. |
| Interpretation | interpretation | The assessment made based on the result of the observation, for example whether the result is normal or abnormal, or high or low. If a coding is provided, the code SHALL be from FHIR Observation Interpretation ValueSet. |
| Comments about the result | comment | May include for example statements about significant, unexpected or unreliable values, or information about the source of the value where this may be relevant to the interpretation of the result. |
| Reference range | referenceRange | A reference range may be given to provide guidance on how to interpret the value by comparison to a normal or recommended range. |
Elements in the profile filled by the Kanta PHR platform
| Content | Name in structure | Description / Type of information |
|---|---|---|
| Application that created or updated the observation | extension: creatingApplication |
Is used to represent information about the application (id and name) that created or updated the resource. See the definition for the Finnish PHR Application Information extension. Kanta PHR platform will fill in this data automatically to each stored observation (if the application has entered some data in this extension, it will be overwitten). |