One Global Passport · Healthcare configuration

Healthcare

The Healthcare package configures the one ENTITY Global Passport for healthcare workflows. It does not create a separate healthcare sovereignty protocol.

Mappings

HL7 FHIR · DICOM. These are correspondence mappings only. FHIR and DICOM remain externally authoritative for their standards; ENTITY does not claim normative equivalence.

Required deployment facts

organization
jurisdiction
authority_source
privacy_policy

A package with placeholder/CONFIGURE-ME values is not a production deployment.

What ENTITY contributes

Persistent identity/authority, rights and consent context, evidence/provenance, portable passport state, versioned mappings, recoverability and auditable events. A provider that hosts a clinical system does not become the sovereign authority merely through custody.

Typical deployment path

select package → configure organization/jurisdiction/authority/privacy facts → connect governed systems/data → ingest → issue/verify passport → run package conformance → deploy

Integrity

Historical sealed package SHA-256: b4e901ce37f696fa10666839cb8d3cacbd1fe663070667ca1767a6245e7cf939. Repository package verification uses python tools/verify_package.py.

Boundary

Package validation does not establish PHIPA/HIPAA or other regulatory compliance, clinical truth, legal title or independent security review. Those require deployment-specific evidence and assessment.