This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201709 Implantables Tracking"

From HL7Wiki
Jump to navigation Jump to search
 
(35 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
</noinclude>
 
</noinclude>
 
[[Category:201709_FHIR_Connectathon_Track_Proposals|Sept 2017 Proposals]]
 
[[Category:201709_FHIR_Connectathon_Track_Proposals|Sept 2017 Proposals]]
−
__NOTOC__
+
{| align="right"
 +
| __TOC__
 +
|}
 
=Track Name=
 
=Track Name=
 
Point-of-care Medical Device and Implantable Tracking
 
Point-of-care Medical Device and Implantable Tracking
Line 13: Line 15:
 
==Justification==
 
==Justification==
 
* Implantable medical devices are costly and concerns about illegitimate (i.e., counterfeit, stolen) products has become a global issue
 
* Implantable medical devices are costly and concerns about illegitimate (i.e., counterfeit, stolen) products has become a global issue
 +
* By 2021 all medical devices that may be used in a point-of-care procedure will be labeled using FDA UDI that will also relate to software/firmware release
 
* Post-market surveillance of implantable medical devices can be challenging
 
* Post-market surveillance of implantable medical devices can be challenging
 
* Implantable medical device adverse events and recalls pose a patient safety issue
 
* 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
 
* 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   
+
* A consistent device identification scheme closes the loop on data acquisition at the point-of-care to support reporting of medical device data   
−
** Medical device data used for:
+
* Medical device data used for:
 
*** Continuum of care (e.g., Discharge Summary, Referrals)
 
*** Continuum of care (e.g., Discharge Summary, Referrals)
 
*** Registries (e.g., Total Joint Registry)
 
*** Registries (e.g., Total Joint Registry)
Line 27: Line 30:
 
* Increase accurate medical device data capture at the point-of-care
 
* Increase accurate medical device data capture at the point-of-care
 
** Eliminates human error from manual medical device data entry
 
** Eliminates human error from manual medical device data entry
 +
[[File:Implantable workflow.png|520 px]]
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==
 
[mailto:ioana.singureanu@bookzurman.com Ioana Singureanu, VA/BZI], Skype: ioanasingureanu
 
[mailto:ioana.singureanu@bookzurman.com Ioana Singureanu, VA/BZI], Skype: ioanasingureanu
−
See [[Connectathon_Track_Lead_Responsibilities]]
+
<!-- See [[Connectathon_Track_Lead_Responsibilities]] -->
  
 
==Expected participants==
 
==Expected participants==
−
* Department of Veterans Affairs
+
* Department of Veterans Affairs - "Medical DeviceTracker"
−
* Magpie360
+
* Magpie360 - "Medical DeviceTracker"
−
* Eversolve, LLC
+
* Eversolve, LLC:  "Medical Device Server"
  
 
==Roles==
 
==Roles==
−
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
+
The test roles for this track are based on the IHE PCC PMDT Actors below:
−
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
+
<div style="display: inline; width: 600px; float: right;"></div>
−
===Point-of-Care Medical Device Tracker===
+
[[File:Actors-pmdt.png|490 px]]
−
*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===
+
===Point-of-Care Medical Device <u>Reporter</u>===
−
*FHIR server, exposes Device, Procedure - references Patient
+
*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 a 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 <u>Server</u>===
 +
*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 <u>Requester</u>===
 +
*This role is played by any information system that requires to compile an implantable device list for patient, evaluate outcomes  based on device type (i.e. DI), respond manufacturers' recalls, and address patient safety events.
 +
 
 
==Scenarios==
 
==Scenarios==
 
The following is a summary test cases proposed for  
 
The following is a summary test cases proposed for  
Line 49: Line 60:
 
##UDI and DI only
 
##UDI and DI only
 
##UDI and DI and optional attributes
 
##UDI and DI and optional attributes
−
# Start procedure...
+
# Start procedure at the point of care. This may an infusion procedure, a diagnostic procedure using a device, a monitoring session, etc. The Procedure resource specifies the status as "in-progress" and the start of the procedure as well as the coded procedure type, patient, practitioner, etc. At the minimum the patient, the device, and the practitioner known at the point-of-care should be specified.
 
##with externally referenced device
 
##with externally referenced device
−
# Complete procedure
+
# Complete procedure; it marks its status to "completed" and specifies the time it was completed.
 
##with externally referenced device
 
##with externally referenced device
−
# Complete implantable procedure
+
# Complete implantable procedure; this a one-time record that a device, tissue, or tissue products was implated.
−
##with externally referenced device
+
##with externally referenced device; it assumes the device was already registered and its UDI and its other identifiers were captures.
−
##with contained device reference
+
##with contained device reference; the device information is included as "contained" resource in the Procedure.
−
# Search procedures
+
# Search procedures; to compute outcomes, compile implantable device lists for transition-of-care, to respond to recall notifications
 
##by patient
 
##by patient
−
##by optional search parameter
+
##by other optional search parameters
−
# search devices
+
# Search devices; to track device utilization, for quality control, to compute outcomes, compile implantable device lists for transition-of-care, to respond to recall notifications
 +
##by udi-carrier
 
##by patient
 
##by patient
−
##by DI
+
##by udi-di
−
===Register Medical Device or Implantable at the point-of-care===
+
===Register Medical Device or Implantable from the point-of-care===
−
:Action:
+
:Action: The 'Tracker' creates a <code>Device</code> resource (using PUT/update), sets <code>Device.id</code> to a 'GUID', <code>Device.udi.carrierAIDC</code> to the base64-encoded, 'scanned UDI', sets <code>Device.status</code> to 'active'. The <code>Device.patient</code> references is set to external reference previously retrieved <code>Patient</code> resource. (see 'Precondition').
 +
:Precondition: The 'Tracker' queried the <code>Patient</code> resource using the <code>Patient.identifier</code> scanned at the point-of-care. This external references is used in <code>Device.patient</code>.
 +
:Success Criteria: The 'Requester'  queries <code>Device</code> by 'udi-carrier' (expression: <code>Device.udi.carrierHRF | Device.udi.carrierAIDC</code>) 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 <code>Device</code> resource.
 +
[[File:POC Device.png|500 px]]
  
−
:Precondition: <!-- What setup is required prior to executing this step? -->
+
===Complete an Implantable Procedure ===
−
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Action: The 'Tracker' creates a <code>Procedure</code> resource (using PUT/update), sets the <code>Procedure.id</code> to 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.
−
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
+
: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>).
 +
[[File:POC_procedure.png|530 px]]
  
−
===Register Device and Procedure Only===
+
===Start a Point-of-Care Procedure ===
−
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: The 'Tracker' creates a <code>Procedure</code> resource (using PUT/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: <!-- What setup is required prior to executing this step? -->
+
: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: <!-- How will the participants know if the test was successful? -->
+
: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: <!-- Any additional complexity to make the scenario more challenging -->
+
:Bonus point: The 'Requester' searches the <code>Procedure</code> resource based on <code>Procedure.code</code> (expression: <code>code</code>).
  
−
<!-- Provide a description of each task -->
+
===Complete a Point-of-Care Procedure ===
 +
:Action: The 'Tracker' updates the <code>Procedure</code> resource (using PUT/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 'Tracker' submits the same transaction using a "contained" <code>Device</code> resource.
 +
 
 +
[[File:PMDT_start_end.png|520 px]]
  
 
==TestScript(s)==
 
==TestScript(s)==
Line 81: Line 106:
 
These should be committed to SVN under trunk/connectathons/[connectathon]
 
These should be committed to SVN under trunk/connectathons/[connectathon]
 
-->
 
-->
 +
* TestScript resources will be created/registered for Jan FHIR Connectathon
 +
 +
==Outcomes==
 +
* Persisted Device resources and procedures performed at the point-of-care for implants (i.e. Complete POC Procedure) in a new FHIR server.
 +
* We need additional test cases for replacing an implant (i.e.  marking the current Device as "inactive") with another implant and documenting the associated new Implant Procedure.
 +
* Updated several "must support" elements and created the PMDT Device resource. In its next iteration this track will  use
 +
**ImplementationGuide for the overall PMDT integration profile,
 +
**StuctureDefinition resources for each profiles
 +
***Point-of-Care Device profile,
 +
***Point-of-Care Procedure Start,
 +
***Point-of-Care Procedure Complete,
 +
***Complete Implant Procedure.
 +
* This track will repeat at the Jan WGM
 +
* The test cases will be further refined for both the FHIR and IHE Connectathon
 +
* This track will be repeated in January 2018 during the [[201801 Medical Device and Implantables Tracking using UDI]].

Latest revision as of 14:17, 17 October 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
  • By 2021 all medical devices that may be used in a point-of-care procedure will be labeled using FDA UDI that will also relate to software/firmware release
  • 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
  • A consistent device identification scheme 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

Implantable workflow.png

Proposed Track Lead

Ioana Singureanu, VA/BZI, Skype: ioanasingureanu

Expected participants

  • Department of Veterans Affairs - "Medical DeviceTracker"
  • Magpie360 - "Medical DeviceTracker"
  • Eversolve, LLC: "Medical Device Server"

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 a 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 an 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 at the point of care. This may an infusion procedure, a diagnostic procedure using a device, a monitoring session, etc. The Procedure resource specifies the status as "in-progress" and the start of the procedure as well as the coded procedure type, patient, practitioner, etc. At the minimum the patient, the device, and the practitioner known at the point-of-care should be specified.
    1. with externally referenced device
  3. Complete procedure; it marks its status to "completed" and specifies the time it was completed.
    1. with externally referenced device
  4. Complete implantable procedure; this a one-time record that a device, tissue, or tissue products was implated.
    1. with externally referenced device; it assumes the device was already registered and its UDI and its other identifiers were captures.
    2. with contained device reference; the device information is included as "contained" resource in the Procedure.
  5. Search procedures; to compute outcomes, compile implantable device lists for transition-of-care, to respond to recall notifications
    1. by patient
    2. by other optional search parameters
  6. Search devices; to track device utilization, for quality control, to compute outcomes, compile implantable device lists for transition-of-care, to respond to recall notifications
    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 PUT/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 PUT/update), sets the Procedure.id to 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 PUT/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 a Point-of-Care Procedure

Action: The 'Tracker' updates the Procedure resource (using PUT/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 'Tracker' submits the same transaction using a "contained" Device resource.

PMDT start end.png

TestScript(s)

  • TestScript resources will be created/registered for Jan FHIR Connectathon

Outcomes

  • Persisted Device resources and procedures performed at the point-of-care for implants (i.e. Complete POC Procedure) in a new FHIR server.
  • We need additional test cases for replacing an implant (i.e. marking the current Device as "inactive") with another implant and documenting the associated new Implant Procedure.
  • Updated several "must support" elements and created the PMDT Device resource. In its next iteration this track will use
    • ImplementationGuide for the overall PMDT integration profile,
    • StuctureDefinition resources for each profiles
      • Point-of-Care Device profile,
      • Point-of-Care Procedure Start,
      • Point-of-Care Procedure Complete,
      • Complete Implant Procedure.
  • This track will repeat at the Jan WGM
  • The test cases will be further refined for both the FHIR and IHE Connectathon
  • This track will be repeated in January 2018 during the 201801 Medical Device and Implantables Tracking using UDI.
Retrieved from "https://wiki.hl7.org/w/index.php?title=201709_Implantables_Tracking&oldid=147640"