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 40: Line 40:
 
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
 
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
===Point-of-Care Implantable Tracker===
+
===Point-of-Care Medical Device Tracker===
 
+
*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
VA - register medical devices, create/update point-of-care procedure information, query patient based on identifier scanned at the point-of-care
 
 
===Point-of-Care Implantable Registry===
 
===Point-of-Care Implantable Registry===
 
+
*FHIR server, exposes Device, Procedure - references Patient
Eversolve, LLC - "MEdical Device Registry" actor; it exposes Patient, Procedure. and Device resources, it stores information sent by systems at the point-of-care
 
 
 
 
==Scenarios==
 
==Scenarios==
<!-- What will be the actions performed by participants? -->
+
The following is a summary test cases proposed for
 +
# Register (create) device record using
 +
** UDI and DI only
 +
** UDI and DI and optional attributes
 +
# Start procedure...
 +
** with externally referenced device
 +
# Complete procedure
 +
** with externally referenced device
 +
# Complete implantable procedure
 +
** with externally referenced device
 +
** with contained device reference
 +
# Search procedures
 +
** by patient
 +
by optional search parameter
 +
# search devices
 +
** by patient
 +
** by DI
 +
===Register Medical Device or Implantable at the point-of-care===
 +
:Action:
  
===Register Implantable Only===
 
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
 
 
:Precondition: <!-- What setup is required prior to executing this step? -->
 
:Precondition: <!-- What setup is required prior to executing this step? -->
 
:Success Criteria: <!-- How will the participants know if the test was successful? -->
 
:Success Criteria: <!-- How will the participants know if the test was successful? -->

Revision as of 00:41, 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

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Point-of-Care Medical Device Tracker

  • 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

Point-of-Care Implantable Registry

  • FHIR server, exposes Device, Procedure - references Patient

Scenarios

The following is a summary test cases proposed for

  1. Register (create) device record using
    • UDI and DI only
    • UDI and DI and optional attributes
  1. Start procedure...
    • with externally referenced device
  1. Complete procedure
    • with externally referenced device
  1. Complete implantable procedure
    • with externally referenced device
    • with contained device reference
  1. Search procedures
    • by patient

by optional search parameter

  1. search devices
    • by patient
    • by DI

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

Action:
Precondition:
Success Criteria:
Bonus point:

Register Device and Procedure Only

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)