Stream: implementers
Topic: Extensibility
Joanna Gaskill (Nov 01 2017 at 18:10):
We are a bit of a ways off of trying to formally register our extensions but we have a lot of data in our system that we want to be able to exchange in FHIR-compliant APIs but that don't fit within the core specification. Obviously, extensions are our best bet for handling these conditions. My question is that in the pages about extensibility, it discusses two options for registering extensions: submitting them as extensions to be officially ballotted and added (or not) as FHIR-approved extensions and then also having non-ballotted extensions that could be defined by any implementer and that are basically there as a repository to facilitate inter-operability but not in any way sanctioned for HL7. On the latter type, which my organization would want to use a lot, it seems like the ability to register the extensions is not yet built out? when I follow the link provided: http://hl7.org/fhir/registry it's essentially a dead link. is there something I'm missing about how to apply to add things to this registry?
Lloyd McKenzie (Nov 01 2017 at 18:44):
It's taken us forever to get a registry up and running. The official registry is now up in "play around" mode here: https://registry.fhir.org/. We'll be wiping the content in a few weeks and then hopefully starting to use it for real.
Lloyd McKenzie (Nov 01 2017 at 18:44):
We'll be correcting the spec to point to that page in the next release (and might even entertain updating prior versions to point there)
John Moehrke (Dec 01 2017 at 15:54):
When will this reset happen? The registry still has too many experiments (many of my own failed experiments).
Lloyd McKenzie (Dec 01 2017 at 15:56):
@Grahame Grieve ?
Grahame Grieve (Dec 01 2017 at 19:45):
we'll be talking about this in New Orleans
Last updated: Apr 12 2022 at 19:14 UTC
