Skip to content

DetectedIssue Profile

Canonical../StructureDefinition/nexus-emr-core-detectedissue
Statusdraft (experimental) · 1.26.0
BaseDetectedIssue (constraint)
SourceFSH · JSON

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.

Elements / Differential

What this profile constrains beyond DetectedIssue. Anything not listed is unchanged from the base; muted type/cardinality values are the base's, shown for context.

Element Flags Card. Type Description & Constraints
DetectedIssue Nexus EMR DetectedIssue Core
Invariants: detectedissue-mitigation-has-rationale
meta 0..1 Meta
source S 0..1 uri Identifies EMR instance & pipeline version the resource came from i
text S 0..1 Narrative Narrative i
identifier 0..* Identifier Business identifier(s) for the detected issue i
system 1..1 uri i
value 1..1 string i
status S 1..1 code registered | preliminary | final | amended | ... (observation-status) i
code S 0..1 CodeableConcept The kind of issue detected (drug-drug interaction, drug-allergy, etc.) i
severity S 0..1 code i
patient S 0..1 Reference(Patient Profile) The patient the issue was detected for i
implicated S 0..* Reference(Resource) The medication/allergy resources whose combination raised this issue i
mitigation S 0..* BackboneElement The prescriber's recorded decision to proceed despite the issue i
action S 1..1 CodeableConcept What was done -- carries the override rationale in .text i
date S 0..1 dateTime When the override was recorded i
author S 0..1 Reference(Practitioner Profile | PractitionerRole Profile) The practitioner who overrode i