Finnish PHR Patient Profile
NB! Software clients integrated to Kanta PHR can store a Patient resource to Kanta PHR themselves only in the sandbox without authorization functionality (see instructions). In all other environments, the Patient resource is created by Kanta PHR during the authorization code flow.
The Finnish PHR Patient profile constrains FHIR® Patient resource.
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 Finnish PHR Patient
| Content | Name in structure | Description / Type of information |
|---|---|---|
| Unique identifier | identifier | A random uuid identifier assigned to the person. Pseudonym generated by PHR is used In the sandbox with authorization functionality, client test and production environments the Kanta PHR will generate the pseudonym during the auhtorization code flow and maps it to the person's social security number. In unauthorized Sandbox identifier is uuid given by the software supplier. |
Optional elements for Finnish PHR Patient
| Content | Name in structure | Description / Type of information |
|---|---|---|
| Language | language | Language used in the observation stored in Kanta PHR. Language has to be chosen from the FHIR languages ValueSet. |
| Is patient's record in active use? | active | Able to mark if a record is inactive. |
| Languages to use in communication | communication | If no language is specified, this implies that the default local language is spoken. If the language is chosen, it has to be chosen from the FHIR languages. |
Elements in the profile filled by the Kanta PHR platform
| Content | Name in structure | Description / Type of information |
|---|---|---|
| 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). |