Health Information Management

BC-2900 Level 1 Healthcare Providers 5 providers 14 API surfaces 3 rated strong or better

Master patient index, coding operations, release of information, health record lifecycle, clinical registry submissions, and healthcare interoperability operations for the provider organisation.

Health Information Management (BC-2900) is a level-1 business capability in the Healthcare Providers model. The catalog holds 14 API surface(s) from 5 provider(s) that can perform some part of it, 3 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Master Patient Index Management BC-2900.10

Stewardship of the master patient index and resolution of duplicate and overlay records.

1 provider, 4 API surfaces

Coding Operations BC-2900.20

Production coding operations for inpatient and outpatient encounters including audit and backlog management.

no catalog coverage

Release of Information BC-2900.30

Receipt, validation, and fulfilment of requests for protected health information.

1 provider, 2 API surfaces

Health Record Lifecycle BC-2900.40

Lifecycle management of health records from creation through retention and destruction.

no catalog coverage

Clinical Registries & Submissions BC-2900.50

Submission to disease, cancer, trauma, and quality registries.

no catalog coverage

Healthcare Interoperability Operations BC-2900.60

Operation of health information exchange connections, FHIR endpoints, patient-initiated data sharing, and provider directory.

3 providers, 8 API surfaces

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Strong 3 Solid coverage with minor gaps
OptumProviderAccessBulkMemberMatchProviderAccessDaVinciExportProviderAccessDaVinciExportDownloadV3 Ingestion6 APIs61.7DatavantOrder QueriesOrders2 APIs61.3Fasten Healthbridge1 API60.4
Developing 1 Usable, with meaningful gaps to close
Tuva Healthmatchesperson-recordspersonspotential-matches4 APIs44.1
Thin 1 Limited public surface area
Select Medical HoldingsAccount1 API33.9

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Health Information Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →