FHIR Chat · Status Elements & IsModifier · committers

Stream: committers

Topic: Status Elements & IsModifier


view this post on Zulip Grahame Grieve (Dec 13 2017 at 11:08):

GF#13465 proposes a new validation rule. Applying this gives these errors:

  • ERROR @ Appointment.participant.status: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ DeviceComponent.operationalStatus: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ DeviceMetric.operationalStatus: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ Encounter.statusHistory.status: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ Encounter.location.status: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ EpisodeOfCare.statusHistory.status: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ Medication.status: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ Slot.status: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ Substance.status: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)
  • ERROR @ Task.status: Status elements that map to status-codes should be labelled as a modifier (src = ResourceValidator)

@Brian Postlethwaite @Cooper Thompson @Lloyd McKenzie @Todd Cooper @Melva Peters @John Hatem @Eric Haas comments?

view this post on Zulip Brian Postlethwaite (Dec 13 2017 at 11:11):

seems reasonable, except in the PA space, I would suggest would like an exemption for the statusHistory parts

view this post on Zulip Grahame Grieve (Dec 13 2017 at 11:25):

y

view this post on Zulip Eric Haas (Dec 13 2017 at 13:49):

ok by me

view this post on Zulip Lloyd McKenzie (Dec 13 2017 at 16:06):

I'm not sure that the "history" elements are truely modifiers

view this post on Zulip Lloyd McKenzie (Dec 13 2017 at 16:07):

So I'd recommend that we make this a suppressible warning - and we'd suppress it for the statusHistory.status elements


Last updated: Apr 12 2022 at 19:14 UTC