Huli FHIR Core Implementation Guide (R5)
0.1.0 - Release Latin America and the Caribbean

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

Encounter Mapping

Encounter Mapping (R5)

HuliEncounter profiles the FHIR R5 Encounter resource. R5 restructured Encounter substantially; the deltas vs. the R4 IG are called out below.

Huli source FHIR R5 element R4 element (for reference)
encounter completed status = #completed status = #finished
encounter class class[] (CodeableConcept 0..*) class (single Coding)
patient subject (1..1, Reference(HuliPatient)) same
time window actualPeriod period
performing practitioner participant[0].actor participant[0].individual
chief complaint reason.value.concept.text reasonCode.text
recorded diagnoses diagnosis.condition (CodeableReference) diagnosis.condition (Reference)
diagnosis primary/secondary diagnosis.use diagnosis.rank
owning organization serviceProvider same
consultorio location[0].location same

Write behavior: only participant[0].actor is consumed and is treated as a Practitioner. The new R5 subjectStatus element is not profiled.

Location: every encounter records its consultorio, sent as a Location/<id> reference to one of the practitioner's locations (PractitionerRole.location). It may be omitted when the practitioner works at exactly one location or the encounter is bound to an appointment that has a location (sent with such an appointment, it must be the appointment's location); otherwise the create is refused with 422 HPB-00150 (HPB-00151 when the practitioner has none). Under la normativa what counts is the practitioner's normativa configuration: a location configured for them is accepted, one that is not is refused with 403 HPB-00141. One entry only, and create-only — the same contract as the R4 IG's Location section, including the PUT Composition/[encounter id] path for writing a note to an encounter.