Stream: Orders and Observation WG
Topic: Breaking change in FHIR v3 for Device.status
David La Hei (Mar 21 2019 at 15:00):
In one of our products, we use the Device resource for modelling the leads of an ICD (implantable cardioverter-defibrillator). Often, when an ICD is explanted the leads are left behind. We used the Device.status value 'not available' to represent that the leads are inactive but still in the patient. This was based on http://hl7.org/fhir/2017Jan/valueset-devicestatus.html, which states "The Device is no longer available for use (e.g. lost, expired, damaged)" for status value 'not available'.
Later (http://hl7.org/fhir/STU3/valueset-device-status.html), the ValueSet was changed; 'not available' is no longer there, it has been replaced by 'inactive'. However, a comment was added for this particular value: "Note: This means for implanted devices the device has been removed from the patient."
This note causes a breaking change for us, because the leads have not been removed from the patient, they only have been de-activated.
The other available values are not appropriate in this particular case.
I am seeking advice on how to resolve this issue.
Lloyd McKenzie (Mar 21 2019 at 15:25):
For now, you'll need an extension. But submit a change proposal to separate the notion of active/Inactive from implanted/explanted
David La Hei (Mar 21 2019 at 15:42):
Thanks for quick reply Lloyd. Would a change request to STU3 and R4 still be taken into consideration? Or, can we only submit a change request for the current build? With your suggestion to add an extension, do you mean adding our own custom status field with own values?
Lloyd McKenzie (Mar 21 2019 at 16:23):
This change would be something that we'd fix in the CI build for official release in R5. Once released, we can't make substantive changes to published specs.
Last updated: Apr 12 2022 at 19:14 UTC