Stream: Orders and Observation WG
Topic: Device Questions
Grahame Grieve (Apr 02 2019 at 10:16):
Device Version is broken up into components, each with a type, but there is no vocabulary for a type. Most things have a complex string version e.g. 1.35.23-1 (or semver: 1.2.3). What 's the expectation here? a single component? with a type, or not? or is smver supposed to ve set up?
I don't think there's justification for breaking version up. It seems like an extension thing to me at best ....
Grahame Grieve (Apr 02 2019 at 10:17):
or else we better get a good vocab for type and some good documentation
Grahame Grieve (Apr 02 2019 at 10:18):
no, I do not begin to understand .value vs .component here
Grahame Grieve (Apr 02 2019 at 10:20):
what's the relationship between device.url and EndPoint? (@Brian Postlethwaite )
Brian Postlethwaite (Apr 03 2019 at 10:31):
Just rechecking, and there is no documentation on either resource on the boundaries between these!
This should be added to both resources.
Will take this up on the PA call tomorrow - to get a PA viewpoint on it.
Brian Reinhold (May 13 2019 at 14:06):
The version 0..* is for the several different types of versioned items there are in a communicating medical device. Some of these are firmware, software, hardware, protocol, and even something like 'Continua'. Even simple consumer devices have all these. The MDC code system (which is device oriented) has codes for each of these version types. The versions were originally present in the now defunct DeviceComponent productionSpecification entry.
Here are some codes from the MDC code system:
description MDC code MDC reference identifier
Hardware revision 531974 MDC_ID_PROD_SPEC_HW
Software revision 531975 MDC_ID_PROD_SPEC_SW
Firmware revision 531976 MDC_ID_PROD_SPEC_FW
Protocol revision 531977 MDC_ID_PROD_SPEC_PROTOCOL
Continua version 532352 MDC_REG_CERT_DATA_CONTINUA_VERSION
Brian Reinhold (May 15 2019 at 09:34):
@Brian Postlethwaite I should add that there USED to be a FHIR-defined code system for these when there was a DeviceComponent resource and there was a productionSpecification element in it. The code system contained more than just versions; it also contained the serial number, for example, which was part of the production spec. In the Device-DeviceComponent merge, It was decided to flatten some of the more common fields like serial number and coordinate all the different version types under versions. The special code system disappeared along with the DeviceComponent but the MDC code system always had codes for these items so that is what I use.
Last updated: Apr 12 2022 at 19:14 UTC
