This wiki has undergone a migration to Confluence found Here
Device (QDM)
Revision as of 12:14, 29 March 2018 by FEisenberg (talk | contribs) (Created page with "{|border="1" cellpadding="2" cellspacing="0" | align="center" style="background:#f0f0f0;"|'''QDM Attribute''' | align="center" style="background:#f0f0f0;"|'''QI Core Metadata...")
| QDM Attribute | QI Core Metadata Element | Comment |
| Device Applied | Procedure (the .status metadata allows conformance to the specific QDM datatype context) | Device.status allows active | inactive | entered-in-error | unknown as a required value set; Procedure.status seems more appropriate - constrain the event code to "Completed" |
| Anatomical Approach Site | Procedure.extension (http://hl7.org/fhir/us/qicore/StructureDefinition/qicore-procedurerequest-approachBodySite) | QDM matched to QI Core / FHIR |
| Anatomical Location Site | Procedure.bodySite | Device.location (QI Core only) can indicate where the resource is found, but Procedure seems a better fit for Device, Applied |
| Negation Rationale | Procedure.notDoneReason | QDM matched to QI Core / FHIR |
| Reason | Procedure.reasonCode | QDM matched to QI Core / FHIR |
| Relevant Period | Procedure.performed[x] | QDM matched to QI Core / FHIR [Note that Procedure.performed generally refers to a point in time which implementers should map the the start of the relevant period. In most cases the start and end of the Relevant Period will be the same. |
| Author dateTime | part of FHIR Provenance Resource | FHIR references authorDatetime as part of the provenance resource for all resources. Is authorDatetime still appropriate for this QDM datatype? |
| Code | Procedure.focalDevice | QDM matched to QI Core / FHIR |
| id | Procedure.id | QDM matched to QI Core / FHIR |
| Source | Procedure.performer | QDM matched to QI Core / FHIR |
