Care contacts (v2)
Intended Use: The Care Contacts API is intended to be used for fetching all care contacts for a given patient within a certain time frame. The intended use for reading data with this API is in first hand that the API is applied for direct access and should not be used to transfer data between caregivers. If it should be used for ''data copying'' between care providers, patient consent must be handled outside the API. The parameters contactAccessZoneUnit represent the PDL Care Unit (Vårdenhet) and contactHeadCareProviderUnit represents PDL Care provider (Vårdgivare) and can be used to evaluate PDL. Specific Rules and Limitations: The consumer of the API is responsible for making sure data retrieved is filtered in compliance with laws and regulations prior to presenting it to any end-users. Message Description: The query result contains a list of care contacts.
Care contacts (v2) is one of 20 APIs that Cambio Healthcare Systems publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Healthcare, Electronic Health Records, Cambio Open Services, Care Contacts, and Encounters. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 1 operation across 1 path, and defines 44 schemas. It is described by OpenAPI 3.0.1, at version v2.
Requests are made against a single base URL, https://api.openservices.cambio.se/api/open/contacts.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Care contacts (v2) declares
2 security schemes
for authenticating requests.
An API key is passed in the header as Ocp-Apim-Subscription-Key (apiKeyHeader).
An API key is passed in the query as subscription-key (apiKeyQuery).
By default, every request must be authenticated, though some operations may also be called without credentials.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.
Schemas 44
The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are Contact (22 properties), ED (20 properties), II (14 properties), ContactEHRExtract (13 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Cambio Healthcare Systems 12
Other APIs Cambio Healthcare Systems publishes across the network.
This is an independent, third-party profile of Care contacts (v2), published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.