Stream: implementers
Topic: Extension Registration
Patrick Shirley (Jun 29 2020 at 07:38):
Hi, just starting out on the use of the Adverse Event HL7 message and we have already identified we will need extensions. Can anyone tell us how long it takes to get an extension registered please?
Jose Costa Teixeira (Jun 29 2020 at 07:56):
For your project, you don't need to register extensions
Jose Costa Teixeira (Jun 29 2020 at 07:57):
(well, you may want to register it locally in your IG)
Jose Costa Teixeira (Jun 29 2020 at 07:57):
unless you want a standard extension, in which case the process would be to start this very discussion and describe what you need (others may need it to, or may help refine what is needed)
Lloyd McKenzie (Jun 29 2020 at 14:13):
If you think you need an extension, the first step is to check for existing extensions. The second is to raise your specific use-case here. It's possible there's already a 'standard' way or existing extension you can use. If not, you may get advised to submit a change request for us to define a standard extension in the next release. (The next release won't be out for another 1.5 years or so though.) If you define your own extension, you need to ensure that the URL of the extension resolves to the extension, that the extension is registered in an appropriate public registry and/or that all downstream systems who might receive instances containing the extension have some other access to the definition of the extension.
Patrick Shirley (Jun 29 2020 at 14:57):
Thanks for the replies. We are in the process of identifying where we need extensions and checking if any currently exist. It would be useful to run this past yourselves. We understand that to use the extended standard with our external community, we will need to register the extensions before we can use with our instance. How long does it take to register a new extension for public usage? Is it quicker to register for private usage first? Is that possible?
Michele Mottini (Jun 29 2020 at 14:58):
You do not need to register an extension to use it
Mareike Przysucha (Jun 29 2020 at 15:04):
Michele Mottini is right. But if you additionally describe your use case to the community, others might
- tell you that they have an extension which you might use, or
- later know, that you already have an extension they might use.
If the demand for some extensions becomes greater, they might be included in the set of standard extensions, like "condition-dueTo". But there is no need to register an extension.
Patrick Shirley (Jun 29 2020 at 15:37):
Thanks, that is really interesting. Thanks for your help. We are finalising our use cases in the next day and should be able to share then. They will be on a spreadsheet. We will be interested to see if the number of extensions can be reduced.
Lloyd McKenzie (Jun 29 2020 at 22:06):
The requirement around extensions is that if you send an instance that contains an extension, the recipient must have access to the extension. Options are:
- have the canonical URL resolve to the extension definition
- put the extension in a common public registry (e.g. registry.fhir.org)
- communicate the extension definition to the receiving system in advance in some other way
#2 is the fastest and easiest, however #1 is desirable if you can manage it. #3 should only be used as a last resort - because it means extra work for both sender and receivers as well as all subsequent downstream receivers
Jay Lyle (Jul 15 2020 at 14:26):
@Brett Marquard Is there any plan to create a US extension registry? Case 1: DEA drug scheduling & other fairly official bits; Case 2: other process-specific things that US stakeholders agree to among themselves. Would that be ONC, NLM, CMS, HHS CIO, Argonauts, Logica?
Last updated: Apr 12 2022 at 19:14 UTC
