Stream: implementers
Topic: device for custom items
Eric Haas (Apr 21 2016 at 16:33):
So I 'm thinking about Device and how it can be implemented for custom stuff like eyeglasses, artificial limbs or hearing aids for a Patient. Triggered by a tracker from Lloyd. I'm thinking these could be profiles on device. This ties into ordering and the various request resources. For example EyeglassPresciption would go away and you would use DeviceUseRequest and reference the eyeglasses profile. The Other thought is create resources for the "common" stuff like eyeglasses/contacts, hearing aids, teeth, limbs.
Lloyd McKenzie (Apr 21 2016 at 20:53):
There's a large set of different types of devices, equipment and general products that may have various manufacturing and/or configuration parameters that will vary by device type. Creating separate resources for each doesn't make a lot of sense to me. While the basic optical characteristics for vision prescriptions haven't changed much over the years, there are some new things (contacts rather than glasses, tinting, etc.) and there'll likely be more new things in the future. Having a generic structure makes more sense to me.
Eric Haas (Apr 21 2016 at 20:54):
Generic Structure? do you meaning profile the Device resource or an eyeglass resource?
Lloyd McKenzie (Apr 22 2016 at 06:04):
I mean a Device resource (or at least a DeviceRequest resource)
Last updated: Apr 12 2022 at 19:14 UTC
