Finnish PHR Nutrition Base profile
Finnish PHR Nutrition Base Profile for FHIR® Observation 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 nutrition related 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 Nutrition profiles
Content | Name in structure | Description / Type of information |
---|---|---|
Language | language | Language with which the observation has been stored in Kanta PHR. Language SHALL be chosen from the FHIR languages ValueSet. |
Narrative | text | A text summary 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 nutrition related data SHALL have the category 'nutrition' (from Finnish PHR Observation Category ValueSet). |
Code of the observation | code | Determines what the observation is (ie. the amount of fluid intake, calorie intake etc.). Codes are allowed only from the LOINC code system. 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 observation | effective[x] | Clinically relevant time or time-period for 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. In some cases, a time-period may be given. |
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 Nutrition profiles
Content | Name in structure | Type of information |
---|---|---|
Actual result | value[x] | Includes the observation result, for example in a calorie intake observation the actual amount of calories. The unit of measurement that SHALL be used will be determined in the derived profiles for each different type of observation. |
Interpretation | interpretation | The assessment made based on the result of the observation, for exapmle 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. |
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). |