Context that connects.

Auteva created Health Context Protocol™ (HCP) to connect healthcare systems records & authorized agents while preserving context.

Auteva created Health Context Protocol™ (HCP) to connect healthcare systems records & authorized agents while preserving context.

Auteva created Health Context Protocol™ (HCP) to connect healthcare systems records & authorized agents while preserving context.

Radiology specialist reviewing medical images across computer monitors

A record needs more than a destination.

A record needs more than a destination.

A record needs more than a destination.

Know Source

Verify Authority

Share with Purpose

Authorized Agents

Clinician pointing to documentation while discussing medical details

Identify the original system and record before exchange.

Provider and laboratory records

Imaging reports and documents

Source and date retained

Know Source

Verify Authority

Share with Purpose

Authorized Agents

Clinician pointing to documentation while discussing medical details

Identify the original system and record before exchange.

Provider and laboratory records

Imaging reports and documents

Source and date retained

Different formats. Connected context.

FHIR, HL7 v2, C-CDA, DICOM, X12, NCPDP, PDFs, scans and faxes. HCP works across existing formats without replacing the original records.

HCP bringing different supported record formats into source-linked health context

Integrates with existing EHR environments.

4,100+

4,100+

Hospitals

Hospitals

75,000+

75,000+

Care locations

Care locations

Permission to act is not permission to read.

An authorized agent can coordinate a record transfer without reading the record itself.

HCP Authorization

hcp_context:

hcp_context:

requester: ai_agent

requester: ai_agent

authority: verified

authority: verified

purpose: continuity_of_care

purpose: continuity_of_care

permissions:

permissions:

action: record_transfer

action: record_transfer

content: not_disclosed

content: not_disclosed

destination: approved_system

destination: approved_system

record:

record:

format: native

format: native

provenance: retained

provenance: retained

audit: recorded

audit: recorded

How HCP connects systems.

How HCP connects systems.

How HCP connects systems.

HCP connects existing systems without replacing them. Organizations retain control over access, records and integrations.

01

Through Auteva Gateway

Connect healthcare platforms through Auteva’s gateway.

01

Through Auteva Gateway

Connect healthcare platforms through Auteva’s gateway.

01

Through Auteva Gateway

Connect healthcare platforms through Auteva’s gateway.

02

Direct HCP-to-HCP

Exchange permitted context directly between compatible systems.

02

Direct HCP-to-HCP

Exchange permitted context directly between compatible systems.

02

Direct HCP-to-HCP

Exchange permitted context directly between compatible systems.

Medical colleagues reviewing clinical information

Why HCP

Clearer handoffs

Keep records linked to their original sources across care teams.

Controlled automation

Let agents complete approved tasks without unrestricted access.

Existing infrastructure

Connect existing healthcare systems without replacing workflows.

Questions about HCP.

For integrations and partnerships, contact Auteva.

What is HCP?

What is HCP?

Which healthcare records and formats can HCP work with?

Which healthcare records and formats can HCP work with?

Does HCP replace FHIR or an EHR?

Does HCP replace FHIR or an EHR?

Can authorized agents use HCP?

Can authorized agents use HCP?

Who decides what can be shared?

Who decides what can be shared?

Does HCP require Auteva or PatientLayer?

Does HCP require Auteva or PatientLayer?

Will records automatically appear in an EHR?

Will records automatically appear in an EHR?

Security & Compliance

Healthcare privacy, independently audited controls, and certified security.

HIPAA / HITECH

SOC 2 Type II

SOC 2 Type I

CSTAR