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

HIP EHRbase Item Tag Experimental API

Experimental EHRbase API for attaching, reading and deleting ITEM_TAG key/value annotations on EHR_STATUS and COMPOSITION versioned objects, addressed by openEHR path. 2 paths / 6 operations. Marked experimental by the provider.

HIP EHRbase Item Tag Experimental API is one of 5 APIs that vitagroup publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include openEHR, Tagging, and Experimental. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 2 paths, organized into 2 resource areas, and defines 1 schema. It is described by OpenAPI 3.0.1, at version v1.

Requests are made against a single base URL, http://localhost:8080/ehrbase.

6 operations 2 paths 1 schemas 2 DELETE2 GET2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v1
Base URL
https://sandkiste.ehrbase.org/ehrbase
License
Resource Areas
2

Paths & Operations 6

Across 2 paths, the API surfaces 6 operations — 2 DELETE, 2 GET, 2 PUT. They span 2 resource areas: EHR_STATUS ITEM_TAGS, COMPOSITION ITEM_TAG. Each is listed below with its method, path, parameters, and response codes.

EHR_STATUS ITEM_TAGS 3
GET
/rest/experimental/tags/ehr/{ehr_id}/ehr_status/{versioned_object_uid}/item_tag
Get tags
getEhrStatusItemTags 6 params → 200
PUT
/rest/experimental/tags/ehr/{ehr_id}/ehr_status/{versioned_object_uid}/item_tag
Create or Update tags
upsertEhrStatusItemTags 5 params body → 200
DELETE
/rest/experimental/tags/ehr/{ehr_id}/ehr_status/{versioned_object_uid}/item_tag
Deletes tags
deleteEhrStatusItemTags 4 params body → 204
COMPOSITION ITEM_TAG 3
GET
/rest/experimental/tags/ehr/{ehr_id}/composition/{versioned_object_uid}/item_tag
Get tags
getCompositionItemTags 6 params → 200
PUT
/rest/experimental/tags/ehr/{ehr_id}/composition/{versioned_object_uid}/item_tag
Create or Update tags
upsertCompositionItemTags 5 params body → 200
DELETE
/rest/experimental/tags/ehr/{ehr_id}/composition/{versioned_object_uid}/item_tag
Deletes tags
deleteCompositionItemTags 4 params body → 204

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ItemTagDto (7 properties). Each schema is shown below with its type and property counts.

ItemTagDto
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vitagroup-hip-ehrbase-item-tags.json Raw ↑

Other APIs vitagroup publishes across the network.

HIP EHRbase openEHR REST API
HIP EHRbase Admin API
HIP EHRbase Enterprise API
EHRbase Sandbox (live springdoc api-docs)
Where this information came from

This is an independent, third-party profile of HIP EHRbase Item Tag Experimental API, 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.