iCure. eHealth Solutions
  • Developer Documentation
  • iCure Software Modules
  • Get Started
    • Create your own Database
      • Receive an invitation
      • Create new User
      • Create a new Healthcare Party
    • Structure your Database
    • Access your database
    • Use the Console
  • Data Stack Module
    • The Data Stack
      • Install iCure
      • Get Started with a Database
    • iCure Data Model
      • Overview
      • User
        • Permission
      • Healthcare Party
      • Patient
        • Insurability
        • Relationship
        • Patient Hcp care period
          • Referral period
      • Contact
        • Service
          • Content
            • Medication
              • Regimen item
            • Measure
        • SubContact
      • Healthcare Element
        • Care team member
        • Healthcare approach
      • Form
      • Additional Classes
        • AccessLog
        • Address
          • Telecom
        • Message
        • Document
        • FilterChain
          • Filter
          • Predicate
        • Group
        • Insurance
        • Invoice
          • Invoicing code
        • Tarification
          • Valorisation
    • Hybrid Cloud Storage
    • Mobile/Web SDKs
      • JavaScript/Typescript
        • Setting up your environment
        • Logging in
        • Managing patients
        • iCure for MedTech: Getting Started
          • Exchange data using FHIR model
          • Exchange data using iCure SDK
      • Java/Kotlin
      • Swift/Objective C
    • REST API calls
      • User
      • Patient
      • HealthcareParty
      • Contact
      • HealthcareElement
      • Form
      • Document
      • Message
      • Invoice
      • Additional endpoints
        • AccessLog
        • Authentication
        • Codification
        • Document template
        • Entity reference
        • Entity template
        • Insurance
        • Receipt
        • Tarification
    • Access Rights management
    • End-to-End-Encryption
    • ATNA Audit Records
  • Interoperability Module
    • IHE XDS calls
      • The XDS Concept
      • ITI-18 get associations api call
      • ITI-41 provide and register document set api call
      • Iti-42 register document set api call
    • IHE IPS call
      • The IPS Concept
    • FHIR API Data Exchange
      • The FHIR Concept
    • Freehealth Connector 🇧🇪
    • Encrypted Data Exchange
      • Internal
      • External
  • Customizable Features Module
    • Input Forms
    • Medical Records
    • Data Dashboards
    • Custom Connectors
    • Secure Log-in App
  • Support
    • Download
    • Contact Us
  • Advanced topics
    • Healthcare Data
      • Business intelligence
      • Anonymized Data
    • Encryption Key Creation and Storage
    • Multi-Master database replication
    • Cross Databases Sharing
    • Complex queries
Powered by GitBook
On this page

Was this helpful?

  1. Data Stack Module
  2. iCure Data Model
  3. Contact

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

id *

The Id of the Service. We encourage using either a v4 UUID or a HL7 Id.

identifier *

contactId

Id of the contact during which the service is provided

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.

secretForeignKeys

The secret patient key, encrypted in the patient document, in clear here.

cryptedForeignKeys *

The public patient key, encrypted here for separate Crypto Actors.

delegations *

The delegations giving access to connected healthcare information.

encryptionKeys *

The contact secret encryption key used to encrypt the secured properties (like services for example), encrypted for separate Crypto Actors.

label *

dataClassName

index

format: int64.

content *

The type of the content recorded in the documents for the service

textIndexes *

valueDate

format: int64.

openingDate

format: int64.

closingDate

format: int64.

formId

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.

endOfLife

Soft delete (unix epoch in ms) timestamp of the object. 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.

medicalLocationId

The id of the medical location where this entity was created.

comment

Text, comments on the Service provided

status

format: int32.

invoicingCodes *

List of invoicing codes

qualifiedLinks *

Links towards related services (possibly in other contacts)

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.

PreviousContactNextContent

Last updated 3 years ago

Was this helpful?

String
List
String
List
List
List
List
List
Map
Map
Map
String
String
Long
Map
Map
Long
Long
Long
String
Long
Long
Long
String
String
String
String
Integer
List
Map
List
List
String