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
Property | Type | Description |
---|---|---|
| The Id of the Service. We encourage using either a v4 UUID or a HL7 Id. | |
| ||
| Id of the contact during which the service is provided | |
| 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 | |
| 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 | |
| List of IDs of all healthcare elements for which the service is provided. Only used when the Service is emitted outside of its contact | |
| List of Ids of all forms linked to the Service. Only used when the Service is emitted outside of its contact. | |
| The secret patient key, encrypted in the patient document, in clear here. | |
| The public patient key, encrypted here for separate Crypto Actors. | |
| The delegations giving access to connected healthcare information. | |
| The contact secret encryption key used to encrypt the secured properties (like services for example), encrypted for separate Crypto Actors. | |
| ||
| ||
| format: int64. | |
| The type of the content recorded in the documents for the service | |
| ||
| format: int64. | |
| format: int64. | |
| format: int64. | |
| ||
| 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. | |
| 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. | |
| Soft delete (unix epoch in ms) timestamp of the object. format: int64. | |
| The id of the User that has created this entity, will be filled automatically if missing. Not enforced by the application server. | |
| The id of the HealthcareParty that is responsible for this entity, will be filled automatically if missing. Not enforced by the application server. | |
| The id of the medical location where this entity was created. | |
| Text, comments on the Service provided | |
| format: int32. | |
| List of invoicing codes | |
| Links towards related services (possibly in other contacts) | |
| 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 | |
| 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. | |
| The base64 encoded data of this object, formatted as JSON and encrypted in AES using the random master key from encryptionKeys. |
Last updated