Stream: implementers
Topic: deviceusestatement
Sean Mahoney (Apr 22 2020 at 14:00):
Is the DeviceUseStatement at a maturity where it can be used in profiles? We want to capture devices used by patients at the time of the observation and/or assessment. This seems like a good fit, just wondering if it is ready for use.
Jose Costa Teixeira (Apr 22 2020 at 14:16):
- I don't think anyone has challenged the concept for DeviceUseStatement (using or not a device is not a very complex concept), so I personally don't expect any major redesign there - even if we would (just for sake of example) change the name, the resource still makes sense.
Jose Costa Teixeira (Apr 22 2020 at 14:17):
- Looking at Jira, I'd guess the structure of the device is not likely to change in the near future (there are a few issues that will result in some changes for R5 but they are not enormous)
Jose Costa Teixeira (Apr 22 2020 at 14:18):
- Your use case seems to be right in the resource's intended scope (it doesn't seem like an edge case) so any changes should still not impact the applicability of the resource to your use case.
Jose Costa Teixeira (Apr 22 2020 at 14:19):
With this information, I would say that your risk level is pretty low - you should be OK to profile the resource.
Lloyd McKenzie (Apr 23 2020 at 00:58):
Any resource - regardless of maturity - can be used in profiles. However, until the resource is normative, there's always a risk of change - or even the resource going away/being merged into something else/etc. Typically lower maturity resources have less implementation experience, which increases the risk of change
Last updated: Apr 12 2022 at 19:14 UTC
