FHIR Chat · creating a choice of identifiers using slicing · conformance

Stream: conformance

Topic: creating a choice of identifiers using slicing


view this post on Zulip Eric Haas (Nov 08 2018 at 03:55):

The DEQM requirement is for organization is to provide at least a provider NPI or an EID for an organization. There were some other requirements such a aligning identifier type with NPI or EID. so THIS is what I came up with to try to essentially create a choice of identifier systems but allow for other identifiers too.... @Richard Ettema created a tracker finding issue with it and preapplied THIS which is prettier but does not constrain to require either an NPI or EID - you could add another identifier. What is the best way to do this? I'm thinking Richards slicing plus an invariant requiring one or the other identifier system? @Lloyd McKenzie @Michel Rutten ?

view this post on Zulip Brian Postlethwaite (Nov 08 2018 at 08:38):

Given both identifiers have knows systems, create an invariant at the top level that checks for one of them.

view this post on Zulip Lloyd McKenzie (Nov 08 2018 at 12:35):

Agree. @Richard Ettema's approach plus an invariant based on identifier.system should give you what you're looking for - and be relatively "pretty" - i.e. readable & understandable by most folks.

view this post on Zulip Eric Haas (Nov 08 2018 at 16:50):

thanks!

view this post on Zulip Richard Townley-O'Neill (Nov 08 2018 at 23:07):

In HL7 AU we slice the same way but constrain the value of type differently. See http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-organisation.html .

I think that the constraint dv-1 in Richard Ettema's design should have 'and' instead of 'or', as if both identifiers are supplied you will want both to have the correct type, not just one of them:
" If present, Identifier.type SHALL be 'http://hl7.org/fhir/v2/0203|PRN' when Identifier.system = 'http://hl7.org/fhir/sid/us-npi',
and
Identifier.type SHALL be 'http://hl7.org/fhir/v2/0203|TAX' when Identifier.system = 'urn:oid:2.16.840.1.113883.4.4'."

view this post on Zulip Richard Townley-O'Neill (Nov 09 2018 at 00:46):

My explanation was wrong, the problem with 'or' is worse

as if both identifiers are supplied you will want both to have the correct type, not just one of them

with an 'or', if you have an identifier with a system that is neither 'http://hl7.org/fhir/sid/us-npi' nor 'urn:oid:2.16.840.1.113883.4.4', the invariant will be satisfied.


Last updated: Apr 12 2022 at 19:14 UTC