-
Enhancement
-
Resolution: Delivered
-
Minor
-
None
The MAT currently supports a set of general relationship operators that were never defined in any QDM specification. In addition, these operators are not currently used by any published MU-2 measures.
The following table describes the operator and the definition from the MAT User Guide (apologies for less-than-optimal formatting in Jira):
Relationship | Code | Definition |
---|---|---|
authorized by | AUTH | 'A' is authorized or certified by 'B' This relationship is provided to allow a measure developer to specify that a patient has provided consent. |
causes | CAUS | 'A' caused 'B' An assertion that an act was the cause of another act. Examples:
|
is derived from | DRIV | 'A' is derived from 'B' This relationship is provided to allow a measure developer to be able to indicate a value that is calculated from other values. An anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate- observations. |
has goal | GOAL | 'A' has goal of 'B' A goal that one defines given a patient’s health condition. Subsequently planned actions aim to meet that goal. 'A' is an observation, while 'B' must be an observation in goal mood. |
has outcome | OUTC | 'A' has outcome of 'B' An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called “post- conditional”.) Example: The outcome of a diagnostic study was ‘x’ diagnosis |
The QDM Management Team suspects that some of the above relationships may not be applicable in the context of QDM and the existing QDM datatypes. The QDM User Group should discuss the applicability of each of these.
- relates to
-
QDM-49 Enhance the relationships within the eMeasure specification standards to enable linking of two data elements based on one of their components (patient ID, referral number, etc.)
- Resolved