FHIR Chat · Device.distinctIdentifier · argonaut

Stream: argonaut

Topic: Device.distinctIdentifier


view this post on Zulip Yunwei Wang (Mar 14 2022 at 16:15):

In US Core 3.1.1, Device.distinctIdentifier is marked as MS and mentioned in the narrative "Each Device must support:". In US Core 3.2.0/4.0.0 (and later versions), Device.distinctIdentifier is NOT marked as MS but still mentioned in the narrative "Each Device must support:". I searched JIRA but could not find ticket related to this change. What is the reason for that mustSupport change? @Eric Haas

view this post on Zulip Brett Marquard (Mar 14 2022 at 16:21):

Funny, @diego kaminker asked me a similar question while I was out last week....Here is the related tracker where we made a bunch of Device changes. My quick read is it was an oversight, but @Eric Haas made these specific changes so would be good for him to confirm.

view this post on Zulip Yunwei Wang (Mar 14 2022 at 17:29):

@Brett Marquard I read that table. My confusion is that that table mentioned 7 identifier elements and six of them are MS. Only the Device.distinctIdentifier is not MS. image.png

view this post on Zulip Eric Haas (Mar 14 2022 at 20:59):

Reviewing Change logs and git history it looks like an error on my part,
un MS the wrong element! Created technical correction tracker. FHIR-36303.
Thanks for catching that!
Eric M Haas, DVM, MS
Health eData Inc
35 Crescent Avenue, Sausalito, CA 94965

view this post on Zulip Yunwei Wang (Mar 15 2022 at 15:37):

Thanks @Eric Haas I would suggest adding 4.0-patch label to this ticket. BTW, I am still not quit sure about the process for adding the "patch" label, like who proposes the label at what meeting, who need to be involved in the discussion, and who makes the final decision.


Last updated: Apr 12 2022 at 19:14 UTC