- see Jira issue
from Todd Cooper, "Provenance Resource Use"
Jira server Jira serverId 9b965702-34a7-3433-bf10-7f66fd69238c key DOF-44
- Q: is it a good way to document all the actors involved in creating and passing through the device data, even the tacet ones?
- Study the Provenance FHIR resource and the W3C Provenance spec that it references
Koichiro Matsumoto (Nihon Kohden)
Paul Schluter (Center for Medical Interoperability)
Martin Rosner (Philips)
John Rhoads (Philips)
With regard to priorities for gaining benefit through the use of FHIR with device data, Reinhold and Rosner emphasized that the main worth of the FHIR Personal Health Device Implementation Guide was in providing a path to FHIR from IEEE 11073-20601-conformant representations, and that the real battle was getting manufacturers to use standards-based data transfer at all instead of yet another one-off protocol that had no common ground with established PHD standards or indeed Bluetooth Low Energy standards that might exist for the type of device being interfaced.
Schlulter and Rhoads talked about the increasingly complex devices like home ventilators being deployed for home use and whether the plan was to extend 20601 to cope with the data complexities that can be expected with this trend. Rosner and Reinhold talked about ongoing modeling discussions in the PHD community, including at the recent meetings at the FDA, and stressed that the focus was very much from the bottom up, firming up the basis for the existing scope of 20601 for, as an example, low end fitness trackers and not increasing the complexity to deal with the high end devices which are of less concern to most PHD users, and which might be more suited PoCD-IG-type approaches, or direct use of HL7 V2.
There was brief discussion of the potential usefulness of the FHIR Provenance resource in device data context, with agreement that the next step would be filling in the details of the use cases that intuition tells us might benefit.