Stream: implementers
Topic: Discriminator for an Observation.identifier
Brian Reinhold (Apr 21 2017 at 14:06):
I need to slice the Observation.identifier for a profile. I want the profile to use a specified form of the identifier.value element for a conditional create in order to prevent data duplication (BTLE PHDs are notorious for sending duplicate data). So I need a discriminator with minimal overhead that will not impinge upon an implementation's possible use of the additional identifier elements. Is the only really sound option to define a system (perhaps a pcha registered URL)?
Lloyd McKenzie (Apr 21 2017 at 15:29):
Well, the system is the namespace for the id, so that only makes sense if you know everything's going to be coming from the same namespace. I'd probably go for an identifier.type as the logical way to slice identifiers most of the time.
Eric Haas (Apr 21 2017 at 23:01):
+1 type
Last updated: Apr 12 2022 at 19:14 UTC
