Care Coordination Management

BC-2820 Level 1 Healthcare Providers 15 providers 28 API surfaces 4 rated strong or better

Coordination of care across providers, settings, and time including referrals, case management, transitions of care, discharge planning, utilisation management, and social-determinant linkage.

Care Coordination Management (BC-2820) is a level-1 business capability in the Healthcare Providers model. The catalog holds 28 API surface(s) from 15 provider(s) that can perform some part of it, 4 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

Referral Management BC-2820.10

End-to-end management of patient referrals from order capture through specialist match, tracking, and closure.

10 providers, 19 API surfaces

Case & Care Management BC-2820.20

Identification, planning, and execution of case-management interventions for high-risk and complex patients.

4 providers, 5 API surfaces

Discharge Planning BC-2820.30

Planning for safe discharge from inpatient care including needs assessment, post-acute placement, and patient education.

1 provider, 1 API surface

Transitions of Care BC-2820.40

Coordination of patient transitions between providers and settings to ensure continuity, safety, and outcome accountability.

no catalog coverage

Utilisation Management BC-2820.50

Review and oversight of admissions, continued stays, and length of stay against medical necessity and utilisation criteria.

no catalog coverage

Social Determinants & Community Linkage BC-2820.60

Identification of social determinants of health and linkage to community resources to support clinical outcomes.

no catalog coverage

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.

Exemplar 2 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 3 Limited public surface area

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 Care Coordination 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 →