How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Journal notes (v2)

Intended Use: The Journal Note API is intended to be used for fetching all journal notes for a given patient within a specified time interval. 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. 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. The parameters AccessZones represent the PDL Care Unit (Vårdenhet) and CareProvider represents PDL Care provider (Vårdgivare) and can be used to evaluate PDL. Message Description : The result returned is a list of journal notes, please see the API definition file for the exact data

Journal notes (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, Journal Notes, and Clinical Documentation. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 1 operation across 1 path, and defines 54 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/journalnotes.

1 operations 1 paths 54 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v2
Base URL
https://api.openservices.cambio.se/api/open/journalnotes
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Journal notes (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.

Operations 1
GET
/
Get Journal Note(s)
get-journal-notes-v2 3 params → 200401403429

Schemas 54

The contract defines 54 schemas that model the data the API accepts and returns. The most detailed are CD (19 properties), II (14 properties), JournalNoteEHRExtract (12 properties), Note (10 properties). Each schema is shown below with its type and property counts.

JournalNoteEHRExtracts
object
List of journal notes where every item in the list holds one(1) journal note.
2 properties
JournalNoteEHRExtract
object
Object describing the contents of the journal note.
12 properties
Note
object
10 properties
Records
object
1 property
RecordType
object
9 properties
OtherValue
object
1 property
ArchetypeRecordsValue
object
1 property
ArchetypeRecord
object
9 properties
EventDateTime
object
2 properties
KeywordToolTypes
string
RecordValue
object
2 properties
JournalValueTypes
string
HCMContact
object
8 properties
II
object
14 properties
TS
QTY
CD
object
19 properties
ED
EDTEXT
object
ST
STNT
object
TELURL
object
TEL
object
10 properties
TELUSE
string
QSETTS
object
8 properties
ANY
object
7 properties
HXIT
object
4 properties
Patient
object
5 properties
PatientName
object
3 properties
PatientGivenName
object
2 properties
Units
object
1 property
Unit
object
10 properties
AccessZones
object
1 property
SimpleUnit
object
2 properties
CareProviders
object
1 property
CareProvider
object
6 properties
CareProviderPosition
object
2 properties
PhoneNumbers
object
1 property
EmailAddresses
object
1 property
UnitAddresses
object
1 property
Phone
object
3 properties
Email
object
3 properties
UnitAddress
object
8 properties
ErrorResponse
object
Generic error response for all systems and applications errors.
4 properties
SecrecyGroups
object
1 property
SecrecyLevels
object
1 property
XSDVersion
object
1 property
XReference
object
1 property
CodingRationale
string
Reliability
string
Scope
string
UncertaintyType
string
UpdateMode
string
JournalNoteEHRExtractsArray
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cambio-healthcare-systems-journal-notes-v2-openapi.json Raw ↑

Other APIs Cambio Healthcare Systems publishes across the network.

Attention signal
Authorizer - OpenId Connect
Booked appointments
Care contacts
Care contacts (v2)
Chemistry lab results (deprecated)
Chemistry lab results (v2)
Diagnosis (deprecated)
Diagnosis (v2)
FHIR R4 Public Profiles
Journal notes (deprecated)
Medication prescriptions (deprecated)
Where this information came from

This is an independent, third-party profile of Journal notes (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.