This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201709 Implantables Tracking"

From HL7Wiki
Jump to navigation Jump to search
Line 78: Line 78:
  
 
===Complete an Implantable Procedure ===
 
===Complete an Implantable Procedure ===
:Action: The 'Tracker' creates a <code>Procedure</code> resource (using POST/update), sets the <code>Procedure.id</code> to a a GUID, <code>Procedure.status</code> to 'completed', <code>Procedure.focalDevice.manipulated</code> to reference the device registered above. The 'Tracker' set the <code>Procedure.performedDateTime</code> to the current date/time.
+
:Action: The 'Tracker' creates a <code>Procedure</code> resource (using POST/update), sets the <code>Procedure.id</code> to a a GUID, <code>Procedure.status</code> to 'completed', <code>Procedure.focalDevice.manipulated</code> to reference the device registered above. The 'Tracker' set the <code>Procedure.performedDateTime</code> to the current date/time. The 'Tracker' specifies the <code>Procedure.code</code> corresponding the implant procedure performed.
 
:Precondition: The 'Tracker' queries the <code>Patient</code> resource using the <code>Patient.identifier</code> scanned at the point-of-care. The 'Tracker' registered a medical device or implantable using a pre-defined GUID as its logical identifier.
 
:Precondition: The 'Tracker' queries the <code>Patient</code> resource using the <code>Patient.identifier</code> scanned at the point-of-care. The 'Tracker' registered a medical device or implantable using a pre-defined GUID as its logical identifier.
 
:Success Criteria: The tracker can retrieve the <code>Procedure</code> resource using its _id. The 'Requester' queries <code>Procedure</code> based on the Patient reference.
 
:Success Criteria: The tracker can retrieve the <code>Procedure</code> resource using its _id. The 'Requester' queries <code>Procedure</code> based on the Patient reference.
 
:Bonus point: The 'Requester' searches the <code>Procedure</code> resource based on <code>Procedure.code</code> (expression: <code>code</code>).  
 
:Bonus point: The 'Requester' searches the <code>Procedure</code> resource based on <code>Procedure.code</code> (expression: <code>code</code>).  
 
[[File:POC_procedure.png|500 px]]
 
[[File:POC_procedure.png|500 px]]
 +
 +
===Start a Point-of-Care Procedure ===
 +
:Action: The 'Tracker' creates a <code>Procedure</code> resource (using POST/update), sets the <code>Procedure.id</code> to  GUID, <code>Procedure.status</code> to 'in-progress', <code>Procedure.focalDevice.manipulated</code> to reference the device registered above. The 'Tracker' set the <code>Procedure.performedPeriod.start</code> to the current date/time.
 +
:Precondition: The 'Tracker' queries the <code>Patient</code> resource using the <code>Patient.identifier</code> scanned at the point-of-care. The 'Tracker' registered a medical device or implantable using a pre-defined GUID as its logical identifier.
 +
:Success Criteria: The tracker can retrieve the <code>Procedure</code> resource using its _id. The 'Requester' queries <code>Procedure</code> based on the Patient reference.
 +
:Bonus point: The 'Requester' searches the <code>Procedure</code> resource based on <code>Procedure.code</code> (expression: <code>code</code>).
 +
 +
===Complete an Implantable Procedure ===
 +
:Action: The 'Tracker' updates the <code>Procedure</code> resource (using POST/update), it sets the <code>Procedure.id</code> to its previously set GUID, <code>Procedure.status</code> to 'completed', <code>Procedure.focalDevice.manipulated</code> to reference the device registered above. The 'Tracker' set the <code>Procedure.performedPeriod.end</code> to the current date/time. The 'Tracker' specifies the <code>Procedure.code</code> corresponding the implant procedure performed.
 +
:Precondition: The 'Tracker' queries the <code>Patient</code> resource using the <code>Patient.identifier</code> scanned at the point-of-care. The 'Tracker' registered a medical device or implantable using a pre-defined GUID as its logical identifier. The 'Tracker' created a first version of the <code>Procedure</code>
 +
:Success Criteria: The tracker can retrieve the <code>Procedure</code> resource using its _id. The 'Requester' queries <code>Procedure</code> based on the Patient reference.
 +
:Bonus point: The 'Requester' searches the <code>Procedure</code> resource based on <code>Procedure.code</code> (expression: <code>code</code>).
 +
 +
[[File:PMDT_start_end.png|520 px]]
  
 
==TestScript(s)==
 
==TestScript(s)==

Revision as of 03:40, 5 September 2017


Track Name

Point-of-care Medical Device and Implantable Tracking

Submitting WG/Project/Implementer Group

This track provides a set of simple test cases for Tracking Medical Devices (i.e. diagnostic, therapeutic, monitoring) and Implantables (biologics/tissue/cells and non-biologics/life-supporting/life-sustaining) at point of care addresses current problems relate to information accuracy and it provides procedure contextual information. This track specifies test cases related FHIR STU3 Procedure and Device resources used to report information from the point-of-care to enterprise system consistent with the IHE PCC Point-of-care Medical Device Tracking Supplement.

Justification

  • Implantable medical devices are costly and concerns about illegitimate (i.e., counterfeit, stolen) products has become a global issue
  • Post-market surveillance of implantable medical devices can be challenging
  • Implantable medical device adverse events and recalls pose a patient safety issue
  • Acquiring medical device data used at the point-of-care is difficult to retrieve for reuse at a later time
  • Closes the loop on data acquisition at the point-of-care to support reporting of medical device data
    • Medical device data used for:
      • Continuum of care (e.g., Discharge Summary, Referrals)
      • Registries (e.g., Total Joint Registry)
      • Payers (e.g., government provided, private insurance)
    • Can associate a medical device used for monitoring a disease or symptom of a disease (e.g., vital sign monitors, pulse oximeters, blood glucose monitors) to a patient for querying the device or procedure using the UDI
  • Increase patient safety
    • Traceability of medical devices (avoid use of counterfeit or illegitimate products)
    • Quality issues identified (e.g., recalls, adverse events)
  • Increase accurate medical device data capture at the point-of-care
    • Eliminates human error from manual medical device data entry

Proposed Track Lead

Ioana Singureanu, VA/BZI, Skype: ioanasingureanu See Connectathon_Track_Lead_Responsibilities

Expected participants

  • Department of Veterans Affairs
  • Magpie360
  • Eversolve, LLC

Roles

The test roles for this track are based on the IHE PCC PMDT Actors below:

Actors-pmdt.png

Point-of-Care Medical Device Reporter

  • Point-of-care client; it registers medical device, creates/updates point-of-care procedure information, query patient based on identifier scanned at the point-of-care. This role is played by an system used to track information about medical devices used at the point-of-care. The device and procedure information are populated at the point-of-care using scanned (AIDC) UDI and patient identifier to simplify the accurate tracking of this information.

Medical Device Server

  • FHIR server, exposes Device, Procedure - references Patient. It is used to persist device and procedure information originating at the point of care. This information is made available to other information systems in the enterprise. This role may be played by a Medical Device Registry or an EHR system.

Point-of-Care Medical Device Requester

  • This role is played by any information system that requires to compile a implantable device list for patient, evaluate outcomes based on device type (i.e. DI), respond manufacturers' recalls, and address patient safety events.

Scenarios

The following is a summary test cases proposed for

  1. Register (create) device record using
    1. UDI and DI only
    2. UDI and DI and optional attributes
  2. Start procedure...
    1. with externally referenced device
  3. Complete procedure
    1. with externally referenced device
  4. Complete implantable procedure
    1. with externally referenced device
    2. with contained device reference
  5. Search procedures
    1. by patient
    2. by other optional search parameters
  6. search devices
    1. by udi-carrier
    2. by patient
    3. by udi-di

Register Medical Device or Implantable from the point-of-care

Action: The 'Tracker' creates a Device resource (using POST/update), sets Device.id to a 'GUID', Device.udi.carrierAIDC to the base64-encoded, 'scanned UDI', sets Device.status to 'active'. The Device.patient references is set to external reference previously retrieved Patient resource. (see 'Precondition').
Precondition: The 'Tracker' queried the Patient resource using the Patient.identifier scanned at the point-of-care. This external references is used in Device.patient.
Success Criteria: The 'Requester' queries Device by 'udi-carrier' (expression: Device.udi.carrierHRF | Device.udi.carrierAIDC) and retrieves one matching resource containing the correct information. The 'Tracker' can retrieve it by logical id/GUID.
Bonus point: specify optional data elements (S, 0..) of the Device resource.

POC Device.png

Complete an Implantable Procedure

Action: The 'Tracker' creates a Procedure resource (using POST/update), sets the Procedure.id to a a GUID, Procedure.status to 'completed', Procedure.focalDevice.manipulated to reference the device registered above. The 'Tracker' set the Procedure.performedDateTime to the current date/time. The 'Tracker' specifies the Procedure.code corresponding the implant procedure performed.
Precondition: The 'Tracker' queries the Patient resource using the Patient.identifier scanned at the point-of-care. The 'Tracker' registered a medical device or implantable using a pre-defined GUID as its logical identifier.
Success Criteria: The tracker can retrieve the Procedure resource using its _id. The 'Requester' queries Procedure based on the Patient reference.
Bonus point: The 'Requester' searches the Procedure resource based on Procedure.code (expression: code).

POC procedure.png

Start a Point-of-Care Procedure

Action: The 'Tracker' creates a Procedure resource (using POST/update), sets the Procedure.id to GUID, Procedure.status to 'in-progress', Procedure.focalDevice.manipulated to reference the device registered above. The 'Tracker' set the Procedure.performedPeriod.start to the current date/time.
Precondition: The 'Tracker' queries the Patient resource using the Patient.identifier scanned at the point-of-care. The 'Tracker' registered a medical device or implantable using a pre-defined GUID as its logical identifier.
Success Criteria: The tracker can retrieve the Procedure resource using its _id. The 'Requester' queries Procedure based on the Patient reference.
Bonus point: The 'Requester' searches the Procedure resource based on Procedure.code (expression: code).

Complete an Implantable Procedure

Action: The 'Tracker' updates the Procedure resource (using POST/update), it sets the Procedure.id to its previously set GUID, Procedure.status to 'completed', Procedure.focalDevice.manipulated to reference the device registered above. The 'Tracker' set the Procedure.performedPeriod.end to the current date/time. The 'Tracker' specifies the Procedure.code corresponding the implant procedure performed.
Precondition: The 'Tracker' queries the Patient resource using the Patient.identifier scanned at the point-of-care. The 'Tracker' registered a medical device or implantable using a pre-defined GUID as its logical identifier. The 'Tracker' created a first version of the Procedure
Success Criteria: The tracker can retrieve the Procedure resource using its _id. The 'Requester' queries Procedure based on the Patient reference.
Bonus point: The 'Requester' searches the Procedure resource based on Procedure.code (expression: code).

PMDT start end.png

TestScript(s)