Stream: committers
Topic: Policy Question on Code Systems / Value Sets
Gino Canessa (Apr 07 2021 at 22:10):
Hey all, I have a quick question about the policy around code systems and value sets published by FHIR. Specifically, I am curious about the inclusion of systems that cannot be expanded without licensing. One example (there are many) is CPT.
I can't remember where I read the policy, and have the vague thought that it was only for sets with required bindings, so thought I would ask the experts.
(it came up because some internal tooling was complaining about sets it could not expand from the core package when processing the spec)
Thanks!
Lloyd McKenzie (Apr 08 2021 at 01:54):
In general, for UV specs, we don't mandate use of terminologies that aren't freely available world-wide. For US-specific specs, we would avoid mandating use of terminologies that weren't either free-for-use in the US context or that weren't already mandated for use by regulation. I.e. we don't want to be in a situation where complying with an HL7 standard forces the incursion of terminology licensing fees that would not otherwise be incurred.
John Moehrke (Apr 08 2021 at 11:52):
is that also true of HL7 published IG? IG published by other organizations would fall under that organizations policy.
Lloyd McKenzie (Apr 08 2021 at 14:48):
Right. This only holds for HL7 International-published IGs (including accelerators). IGs published by other organizations can do as they please.
Gino Canessa (Apr 08 2021 at 14:53):
Thanks Lloyd, so just to make sure - it's fine that these Code Systems and Value Sets are defined in the FHIR core packages, they just can't be used in the FHIR core packages. Right?
Lloyd McKenzie (Apr 08 2021 at 15:42):
They can be used - as example or preferred bindings. But they can't be used with extensible or required bindings without getting special permission.
Last updated: Apr 12 2022 at 19:14 UTC
