Huli FHIR Core Implementation Guide (R4) - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Organization Mapping

Organization Mapping: Huli -> FHIR R4

HuliOrganization represents the Huli organization (the clinic, practice, or health system) that the authenticated client is bound to. The Public API is read-only for Organization: partners cannot create or update organizations through the FHIR surface; provisioning happens during onboarding.

A client may read only the Organization that matches its own organization. Requests for any other Organization.id return 404.

Interactions

Interaction	Supported
read	Yes (own organization only)
vread	No
update	No
patch	No
delete	No
history	No
create	No
search-type	No

The resource is fetched by id only, via GET /fhir/R4/Organization/{id}.

Resource Identity

Huli concept	FHIR path	Cardinality	Must Support	Notes
Organization id (UUID)	Organization.id	1..1	–	UUID of the Huli organization; same identifier emitted on Patient.managingOrganization.reference
Last update	Organization.meta.lastUpdated	0..1	–	Set by the platform

Active flag

Huli concept	FHIR path	Cardinality	Must Support	Notes
Organization status	Organization.active	0..1	Yes	true for active organizations; false for deactivated organizations

Name

Huli concept	FHIR path	Cardinality	Must Support	Notes
Organization name	Organization.name	1..1	Yes	Display name of the organization

Type

When the organization carries a configured type, the Public API emits a single Organization.type entry with the HL7 organization-type system.

FHIR path	Cardinality	Notes
Organization.type[0].coding[0].system	0..1	http://terminology.hl7.org/CodeSystem/organization-type
Organization.type[0].coding[0].code	0..1	Organization-configured type code (e.g., prov for healthcare provider)
Organization.type[0].coding[0].display	0..1	Mirror of the code for human-readable rendering

Elements not emitted by the Public API

The HuliOrganization profile permits identifier, telecom, and address; the Public API does not populate them at this revision. A Huli organization maps to exactly one Organization resource; multi-site operations are not modelled through FHIR Location.