This
page
is
part
of
the
FHIR
Specification
(v3.0.2:
STU
3).
(v3.3.0:
R4
Ballot
2).
The
current
version
which
supercedes
this
version
is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
.
Page
versions:
R5
R4B
R4
R3
R2
Clinical
Decision
Support
Work
Group
|
Maturity Level : 1 | Trial Use | Compartments : Device , Patient , Practitioner |
Detailed Descriptions for the elements in the DetectedIssue resource.
| DetectedIssue | |
| Element Id | DetectedIssue |
| Definition |
Indicates an actual or potential clinical issue with or between one or more active or proposed clinical actions for a patient; e.g. Drug-drug interaction, Ineffective treatment frequency, Procedure-condition conflict, etc. |
| Control | 1..1 |
| Alternate Names | DDI; drug-drug interaction; Contraindication; Alert |
| DetectedIssue.identifier | |
| Element Id | DetectedIssue.identifier |
| Definition |
Business identifier associated with the detected issue record. |
| Note | This is a business identifer, not a resource identifier (see discussion ) |
| Control |
|
| Type | Identifier |
| Requirements |
Allows linking instances of the same detected issue found on different servers. |
| Summary | true |
| DetectedIssue.status | |
| Element Id | DetectedIssue.status |
| Definition |
Indicates the status of the detected issue. |
| Control | 1..1 |
| Terminology Binding | ObservationStatus ( Required ) |
| Type | code |
| Is Modifier | true (Reason: This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid) |
| Alternate Names | status |
| Summary | true |
| Comments |
This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the issue as not currently valid. |
| DetectedIssue.category | |
| Element Id | DetectedIssue.category |
| Definition |
Identifies the general type of issue identified. |
| Control | 0..1 |
| Terminology Binding | Detected Issue Category ( Preferred ) |
| Type | CodeableConcept |
| Alternate Names | type |
| Summary | true |
| DetectedIssue.severity | |
| Element Id | DetectedIssue.severity |
| Definition |
Indicates the degree of importance associated with the identified issue based on the potential impact on the patient. |
| Control | 0..1 |
| Terminology Binding | DetectedIssueSeverity ( Required ) |
| Type | code |
| Alternate Names | severity |
| Summary | true |
| DetectedIssue.patient | |
| Element Id | DetectedIssue.patient |
| Definition |
Indicates the patient whose record the detected issue is associated with. |
| Control | 0..1 |
| Type | Reference ( Patient ) |
| Requirements |
While the subject could be inferred by tracing the subject of the implicated resources, it's useful to have a direct link for query purposes. |
| Summary | true |
| DetectedIssue.date | |
| Element Id | DetectedIssue.date |
| Definition |
The date or date-time when the detected issue was initially identified. |
| Control | 0..1 |
| Type | dateTime |
| Requirements |
No-one can be responsible for mitigation prior to the issue being identified. |
| Summary | true |
| DetectedIssue.author | |
| Element Id | DetectedIssue.author |
| Definition |
Individual or device responsible for the issue being raised. For example, a decision support application or a pharmacist conducting a medication review. |
| Control | 0..1 |
| Type | Reference ( Practitioner | Device ) |
| Summary | true |
| DetectedIssue.implicated | |
| Element Id | DetectedIssue.implicated |
| Definition |
Indicates the resource representing the current activity or proposed activity that is potentially problematic. |
| Control | 0..* |
| Type | Reference ( Any ) |
| Alternate Names | cause |
| Summary | true |
| Comments |
There's an implicit constraint on the number of implicated resources based on DetectedIssue.type; e.g. For drug-drug, there would be more than one. For timing, there would typically only be one. |
| DetectedIssue.detail | |
| Element Id | DetectedIssue.detail |
| Definition |
A textual explanation of the detected issue. |
| Control | 0..1 |
| Type | string |
| Comments |
Should focus on information not covered elsewhere as discrete data - no need to duplicate the narrative. |
| DetectedIssue.reference | |
| Element Id | DetectedIssue.reference |
| Definition |
The literature, knowledge-base or similar reference that describes the propensity for the detected issue identified. |
| Control | 0..1 |
| Type | uri |
| DetectedIssue.mitigation | |
| Element Id | DetectedIssue.mitigation |
| Definition |
Indicates
an
action
that
has
been
taken
or
is
committed
to
|
| Control | 0..* |
| DetectedIssue.mitigation.action | |
| Element Id | DetectedIssue.mitigation.action |
| Definition |
Describes the action that was taken or the observation that was made that reduces/eliminates the risk associated with the identified issue. |
| Control | 1..1 |
| Terminology Binding | Detected Issue Mitigation Action ( Preferred ) |
| Type | CodeableConcept |
| Comments |
The
|
| DetectedIssue.mitigation.date | |
| Element Id | DetectedIssue.mitigation.date |
| Definition |
Indicates when the mitigating action was documented. |
| Control | 0..1 |
| Type | dateTime |
| Comments |
This
|
| DetectedIssue.mitigation.author | |
| Element Id | DetectedIssue.mitigation.author |
| Definition |
Identifies the practitioner who determined the mitigation and takes responsibility for the mitigation step occurring. |
| Control | 0..1 |
| Type | Reference ( Practitioner ) |