Nexus EMR profile for Condition resource, representing health concerns (CII E11) or clinical assessments (CII E34). Constrains necessary elements, requires a Nexus EMR identifier, and adds support for required extensions and security labels.
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.
The specific condition, problem, or diagnosis.
REQUIRED: text element for human readability
OPTIONAL: Standard terminology codes (ICD-10, SNOMED CT, etc.)
OPTIONAL: Raw EMR condition codes for source system preservation
Nexus EMR does not mandate a specific coding system for conditions.
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.
A category assigned to the condition. Distinguishes problem list items from encounter diagnoses.
Binding guidance for downstream converters:
- Conditions sourced from dxresearch (disease registry) → problem-list-item
- Conditions sourced from casemgmt_issue with CPP types (e.g. MedHistory) → problem-list-item
- Conditions referenced from an Invoice line item or appointment → encounter-diagnosis
Comments
Multiple categories can be assigned. Problem list items persist across encounters.
The anatomical location where this condition manifests itself.
Comments
Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension bodySite. May be a summary code, or a reference to a very precise definition of the location, or both.