This wiki has undergone a migration to Confluence found Here
Medical Device Data Sharing with Enterprise Health Systems 180313
Jump to navigation
Jump to search
Back to Medical_Device_Data_Sharing_with_Enterprise_Health_Systems
Meeting Information
Device guidance project Meeting Minutes |
Date: 2018-03-13 Time: 9:00-10:00 ET | ||
Facilitator | Jay Lyle | Note taker(s) | Jay Lyle |
Attendee | Name | Affiliation | |
y | Jay Lyle | JP Systems / VA | |
y | Ioana Singureanu | ||
y | Marti Velezis | ||
y | Greg Staudenmaier | ||
y | Kathleen Connor | ||
y | Jayme Welty | ||
y | Neelima Chennamaraja | ||
Agenda
Agenda Topics
- scope
- FHiR resources that will be profiled for this IG.
- Device, including the harmonized UDI pattern developed by the UDI Project and possible harmonization with medication AIDC barcode/RFID tracking at the point of care. VA has made great progress in patient safety by using barcode medication administration at the point-of-care. For this IG we would like to leverage the known and successful workflow used in the field.
- Procedure -references Condition, Practitioner. Encounter, and , of course, Patient.
- Based on our Connectathon work we identified MedicationAdministration , Medication, Location- optional resources for self-injection device and other home device
- For specialties, we would like to focus on orthopedics/joint replacement/prosthetics and cardiology implant, Other specialties? Womens' health?
- planning
Minutes
Minutes/Conclusions Reached:
- Scope of project, DAM overview
- How differs from UDI, Med Dev projects?
- Use of devices in context of point-of-care procedure; how device is documented.
- implants
- community centers; device back to VA
- Question: identify specialties with special interest (eg ortho, cardio)
- Not to rework device or device source of data
- Focus on capturing device identification in context of procedure (implants, used by, med admin)
- latest use case: self-injectables (procedure: start, stop using device)
- also a device qualifying implantables: implantable tags. Implant can self-identify, or augmented.
- tag may also identify sites/morphologies irrespective of device. auto capture of user, time, place, dose, etc.
- ballot contents
- Ballot: Cross-paradigm IG + DAM additions
- guidance on FHIR profiles, V2
- Include provenance
- suggest example profiles for FHIR pub - Q# next steps
- next steps
- review existing use cases week of 3/13: Team (https://gforge.hl7.org/gf/project/dcmmd/frs/)
- Confirm boundary with UDI DAM: Ioana, Marti. 3/16
- Add 2 use cases to DAM: Ioana 3/19
- 3/20 meeting - review new use cases
- review point of care procedure workflow examples. prioritize ortho, then cardio
- 3/26 present to PC
- 3/27 last meeting before submission
- Note: This schedule is quite aggressive.
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.