Nexus EMR profile for DetectedIssue -- drug-drug and drug-allergy interaction findings raised during prescribing, and the prescriber's recorded override of them. First pass: models the override audit trail; the severity mapping is not yet settled.
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.
Key
Type
Expression
Rendered as
Description
code
coded
code
The kind of issue detected (drug-drug interaction, drug-allergy, etc.) i
The kind of issue detected (drug-drug interaction, drug-allergy, etc.)
Definition
Identifies the general type of issue identified.
Comments
Currently written text-only by the screening layer. Text-only is conformant (CodeableConcept), so readers MUST NOT index positionally into code.coding -- see the text-only-concept rule. Coding this against detectedissue-category is first-pass follow-up, not settled.
Indicates the degree of importance associated with the identified issue based on the potential impact on the patient.
Comments
⚠ FIRST PASS -- NOT SETTLED. The screening engine has its own severity scale and the mapping onto the R4 detectedissue-severity required binding has not been agreed. Do not treat the current values as a contract.
registered | preliminary | final | amended | ... (observation-status)
Definition
Indicates the status of the detected issue.
Comments
The Rx module writes final for a screening result it stands behind. This element is NOT the override axis -- an overridden issue stays final and gains a mitigation; it does not become cancelled. Readers must not infer 'resolved' from status.