Primary buyer
Health systems and healthtech platforms
Proposed solution design
A patient-record export for an approved purpose needs accountable authority, exact scope, and evidence from the system that applies it.
Industry designs describe target integrations. A page or example operation is not an available adapter, registered predicate, or deployed service.
Health systems and healthtech platforms
A patient-record export for an approved purpose
Patient resource reference, dataset, purpose policy, destination, record count, and expiry
Complement existing EHR permissions and SMART on FHIR authorization. Enforce export restrictions at the data service; keep protected health information outside the closed action envelope.
No EHR integration or clinical-treatment authorization is claimed. Patient safety, emergency access, professional accountability, and a regulated design partner are required.
Use the existing credential-rotation evaluation to inspect shared authorization mechanisms. It does not execute this industry-specific action. A domain demonstration requires its own adapter, protected destination, and observed effect.
Use case / Health systems and healthtech platforms
Illustrative integration review. These controls explain the design; they do not submit requests, grant authority, or execute an action.
Stage 1
A patient-record export for an approved purpose
Use the existing Living Intent Contract and closed predicate envelope. New domain constraints require registered typed predicates, documented semantics, and one deterministic evaluator. Domain content and secrets stay outside the envelope. No new universal protocol or compatibility certification is claimed.
These external specifications and programs inform integration design. Links do not establish a partnership, implemented adapter, or 2AYE conformance.