Service
This entity represents a Service. A Service is created in the course a contact. Services include subjective information provided by the patient, such as complaints, reason for visit, feelings, etc. or objective information like bio-metric measures (blood pressure, temperature, heart beat, etc.), or physical exam description, diagnosis, prescription, integration of lab reports from another healthcare party, action plan, etc. Any action performed by the healthcare party which is relevant for the healthcare element of a patient is considered a service. The services can be linked to healthcare elements or other structuring elements of the medical record
Properties
subContactIds
List of IDs of all sub-contacts that link the service to structural elements. Only used when the Service is emitted outside of its contact
plansOfActionIds
List of IDs of all plans of actions (healthcare approaches) as a part of which the Service is provided. Only used when the Service is emitted outside of its contact
healthElementsIds
List of IDs of all healthcare elements for which the service is provided. Only used when the Service is emitted outside of its contact
formIds
List of Ids of all forms linked to the Service. Only used when the Service is emitted outside of its contact.
encryptionKeys *
The contact secret encryption key used to encrypt the secured properties (like services for example), encrypted for separate Crypto Actors.
created
The timestamp (unix epoch in ms) of creation of this entity, will be filled automatically if missing. Not enforced by the application server. format: int64.
modified
The date (unix epoch in ms) of the latest modification of this entity, will be filled automatically if missing. Not enforced by the application server. format: int64.
author
The id of the User that has created this entity, will be filled automatically if missing. Not enforced by the application server.
responsible
The id of the HealthcareParty that is responsible for this entity, will be filled automatically if missing. Not enforced by the application server.
codes *
A code is an item from a codification system that qualifies the content of this entity. SNOMED-CT, ICPC-2 or ICD-10 codifications systems can be used for codes
tags *
A tag is an item from a codification system that qualifies an entity as being member of a certain class, whatever the value it might have taken. If the tag qualifies the content of a field, it means that whatever the content of the field, the tag will always apply. For example, the label of a field is qualified using a tag. LOINC is a codification system typically used for tags.
encryptedSelf
The base64 encoded data of this object, formatted as JSON and encrypted in AES using the random master key from encryptionKeys.
Last updated
Was this helpful?