Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R4
-
Orders & Observations
-
Device
-
-
Marti Velezis / Javier Espina : 10-0-0
-
Enhancement
-
Compatible, substantive
-
R5
Description
The Device resource also covers software systems and with the proliferation of health apps, I suspect this use case may become more prominent (that was what brought me to this resource). However, the current documentation has very little mention of this use case (I was actually unsure about whether this was even the appropriate resource after reading the R4 docu). I therefore propose that the documentation be updated in the following ways.
- Including the software/app use case more prominently in the general description
- Providing some rudimentary guidance on how to use the resource for this case. For instance, it would be great to have some guidance on using codes to represent the (semver) version of the software (in the version.type element) and for documenting conformance to a given version for FHIR (in the specialization element).
- Adding an example showing how to use for a software system.
Related Zulip discussion: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Representing.20a.20piece.20of.20software.20in.20FHIR