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.
The specific procedure that was performed.
REQUIRED: text element for human readability
RECOMMENDED: Standard terminology codes (CPT, SNOMED CT, LOINC, etc.)
OPTIONAL: Raw EMR procedure codes for source system preservation
Nexus EMR does not mandate a specific coding system for procedures.
The text element ensures human readability even when coded values are not recognized.
Comments
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.
The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text.
Comments
Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure.