Defines the Encounter resource constraints for the Nexus EMR project (CII), conforming to CA-Core+ requirements.
Salient fields
The profile's synthesized-accessor contract: fields TypedFhir surfaces as first-class typed properties, each computed from the instance by a restricted FHIRPath expression. See Salient Fields for what they are, how they shape LLM contexts, and how to declare them.
Classification of patient encounter, from the required v3-ActEncounterCode binding.
Ambulatory (AMB) is the common case and the expected default for a clinic visit. It is NOT fixed:
a virtual encounter is VR and an admission is IMP, and writing AMB for either asserts
something the record does not support.
Comments
Map from the appointment's modality, where one is known. In-person becomes AMB; video,
telephone and secure-message all become VR. That mapping is the one this guide states, and it is
the reason this element is not fixed to AMB -- the modality axis exists precisely to distinguish
a video consult from one in the room, and collapsing it here would leave that distinction living
only on an extension of the Appointment, which not every Encounter has.
A reader should NOT infer scope from the breadth of the binding. Nexus EMR encounters are
predominantly ambulatory; IMP is admitted so that an admission a discharge summary refers to can
be represented at all, not as a statement that inpatient workflows are modelled here.
Specific type of encounter (e.g., consultation, follow-up, emergency).
RECOMMENDED: Standard terminology codes when available
OPTIONAL: Raw EMR codes for source system preservation
Where this code was mapped from a source system's own vocabulary, carry the raw coding alongside the mapped one, flagged userSelected = true. See Carrying the raw code.
Comments
Since there are many ways to further classify encounters, this element is 0..*.
Coded reason the encounter takes place.
RECOMMENDED: SNOMED CT or other standard terminology when available
OPTIONAL: Raw EMR codes for source system preservation
Where this code was mapped from a source system's own vocabulary, carry the raw coding alongside the mapped one, flagged userSelected = true. See Carrying the raw code.
Comments
For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).
Plain text narrative that identifies the resource in addition to the resource reference.
Comments
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.