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

Practitioner Mapping

Practitioner Mapping: Huli -> FHIR R4

HuliPractitioner is read-only on the Public API. Partner systems cannot create or update practitioners through the FHIR surface; provisioning happens through the operator-facing Huli platform.

Interactions

Interaction	Supported
read	Yes
vread	No
update	No
patch	No
delete	No
history	No
create	No
search-type	No

Practitioner is fetched by id only, via GET /fhir/R4/Practitioner/{id}.

Resource Identity

Huli concept	FHIR path	Cardinality	Must Support	Notes
User id (UUID)	Practitioner.id	1..1	–	UUID of the clinician within Huli
Last update	Practitioner.meta.lastUpdated	0..1	–	Set by the platform

Active flag

Huli concept	FHIR path	Cardinality	Must Support	Notes
Active status	Practitioner.active	0..1	Yes	true for active accounts; false for deactivated, suspended, or revoked

Name

The Public API emits exactly one HumanName element with use = official, matching the two-surname pattern used by HuliPatient.

Huli concept	FHIR path	Cardinality	Must Support	Notes
Given name	Practitioner.name[0].given[0]	1..1	Yes	First name of the clinician
Primary surname	Practitioner.name[0].family	1..1	Yes	Primary (first) surname
Second surname	Practitioner.name[0].extension[second-lastname].valueString	0..1	–	Emitted when present; URL https://fhir.huli.ai/r4/StructureDefinition/second-lastname
Use	Practitioner.name[0].use	1..1	–	Always official

Elements not emitted by the Public API

The HuliPractitioner profile permits additional elements (identifier, telecom, gender, qualification); the Public API does not populate them at this revision. Partner systems that need any of those for credentialing or contact routing should resolve them through the operator-facing platform.