Stream: implementers
Topic: Practitioner Extensions
KAVITHA C (May 31 2021 at 12:23):
Hi i am trying to Link Surviving Practitioner after deactivating the existing Practitioner.
Eg. Referencing A from B. after Deactivating B practitioner.
For that i am using extension replaces. in the below format
"extension": [
{
"valueCanonical": "https://rochesterrhio.org/Practitioner?identifier=A",
"url": "http://hl7.org/fhir/StructureDefinition/replaces"
}
],
But i am getting following Error while validating
{ "path": "Practitioner", "message": "The extension http:\/\/hl7.org\/fhir\/StructureDefinition\/replaces is not allowed to be used at this point (allowed = e:ActivityDefinition, e:CapabilityStatement, e:ChargeItemDefinition, e:CodeSystem, e:CompartmentDefinition, e:ConceptMap, e:EffectEvidenceSynthesis, e:EventDefinition, e:Evidence, e:EvidenceVariable, e:ExampleScenario, e:GraphDefinition, e:ImplementationGuide, e:Library, e:Measure, e:MessageDefinition, e:NamingSystem, e:OperationDefinition, e:PlanDefinition, e:Questionnaire, e:ResearchDefinition, e:ResearchElementDefinition, e:RiskEvidenceSynthesis, e:SearchParameter, e:StructureDefinition, e:StructureMap, e:TerminologyCapabilities, e:TestScript, e:ValueSet; this element is [[Practitioner])" }
Could anyone please help me to solve this issue.
Yunwei Wang (May 31 2021 at 15:25):
Each extension has "Context of Use" which specifies which elements could be extended. The error message is pretty clear that Practitioner is not on the list of context of use. So you could raise a JIRA ticket to expand the context of use to cover your use case.
Lloyd McKenzie (May 31 2021 at 23:08):
@Brian Postlethwaite
KAVITHA C (Jun 01 2021 at 06:17):
Thanks Yunwei Wang
I found this extension "http://hl7.org/fhir/StructureDefinition/replaces" under practitioner resource -Profiles & Extensions section. That's why i thought to use this under Practitioner resource. As u mention ,i will do create JIRA ticket. Could you please tell me. where i need to create?
Lloyd McKenzie (Jun 01 2021 at 14:00):
@Grahame Grieve Why is this showing up on Practitioner when it doesn't have a context of Practitioner?
Grahame Grieve (Jun 02 2021 at 00:54):
I don't know. needs a task to fix
Lloyd McKenzie (Jun 02 2021 at 03:25):
@KAVITHA C would you be willing to submit a change request for us to fix the rendering issue? (And another change request to expand the scope to support Practitioner as a scope for this extension.)
KAVITHA C (Jun 02 2021 at 08:03):
Lloyd McKenzie said:
KAVITHA C would you be willing to submit a change request for us to fix the rendering issue? (And another change request to expand the scope to support Practitioner as a scope for this extension.)
Sure I will do. I didn't create change request before. If any reference steps/guidance, it would be helpful for me.
Lloyd McKenzie (Jun 02 2021 at 13:44):
Awesome! At the bottom of every page in the FHIR spec there's a "propose a change" link. That will take you to HL7's Jira site. If you don't yet have an account, you'll have to click on the button to request one. Accounts are free and open to anyone. We review account requests manually to make sure you're a real human being who seems to have a legitimate reason to be here. Once you've got an account, you can submit changes as you see fit. The process for submitting is pretty clear, but if you have questions, there's documentation here: https://confluence.hl7.org/display/HL7/Specification+Feedback
KAVITHA C (Jun 03 2021 at 12:47):
Lloyd McKenzie said:
Awesome! At the bottom of every page in the FHIR spec there's a "propose a change" link. That will take you to HL7's Jira site. If you don't yet have an account, you'll have to click on the button to request one. Accounts are free and open to anyone. We review account requests manually to make sure you're a real human being who seems to have a legitimate reason to be here. Once you've got an account, you can submit changes as you see fit. The process for submitting is pretty clear, but if you have questions, there's documentation here: https://confluence.hl7.org/display/HL7/Specification+Feedback
Requested account for creating change request
KAVITHA C (Jun 29 2021 at 09:38):
KAVITHA C said:
Lloyd McKenzie said:
Awesome! At the bottom of every page in the FHIR spec there's a "propose a change" link. That will take you to HL7's Jira site. If you don't yet have an account, you'll have to click on the button to request one. Accounts are free and open to anyone. We review account requests manually to make sure you're a real human being who seems to have a legitimate reason to be here. Once you've got an account, you can submit changes as you see fit. The process for submitting is pretty clear, but if you have questions, there's documentation here: https://confluence.hl7.org/display/HL7/Specification+Feedback
Requested account for creating change request
Hi Any update on this?
Lloyd McKenzie (Jun 29 2021 at 14:18):
Hi @KAVITHA C , thanks for reaching out. It looks like the request was approved the same day you made it - but the email you'd specified on registration had a slight typo (gmial.com instead of gmail.com) and so you never got the notification. I've corrected your email address. You should be able to do a password reset with the user id you originally registered with and then be off to the races.
@Joshua Procious - for some reason our process didn't pick up on the email bounce. Is there something we can put in place that might catch this sort of issue going forward?
Joshua Procious (Jun 29 2021 at 17:05):
@Lloyd McKenzie perhaps we can filter from our outlook server. I think that'll be the best place to capture failures because Jira has almost no granular control over handling email's metadata. I'll get with Bryn Evans on it.
KAVITHA C (Jul 01 2021 at 10:50):
@Lloyd McKenzie Thanks for fixing the issue. I have created the JIRA ticket
@Grahame Grieve
Please take a look into it https://jira.hl7.org/browse/FHIR-33001
Lloyd McKenzie (Jul 01 2021 at 14:52):
Looks good
KAVITHA C (Jul 12 2021 at 06:40):
Lloyd McKenzie said:
Looks good
Thanks for checking. It seems no one assigned for this ticket. Please let me know if any action taken for this ticket
Lloyd McKenzie (Jul 12 2021 at 15:14):
Requests for change will be reviewed by the responsible work group, though it can take weeks (and sometimes months) before it will come up on their agenda. Any change will be effective in R5 (slated for Q3 2022). You'll need to use a custom extension for R4.
KAVITHA C (Jul 15 2021 at 05:48):
Lloyd McKenzie said:
Requests for change will be reviewed by the responsible work group, though it can take weeks (and sometimes months) before it will come up on their agenda. Any change will be effective in R5 (slated for Q3 2022). You'll need to use a custom extension for R4.
Okay thanks. Then I need to create Extension similar to "http://hl7.org/fhir/StructureDefinition/replaces" right? to use it in my practitioner and related person resource
Lloyd McKenzie (Jul 15 2021 at 14:03):
Correct
Last updated: Apr 12 2022 at 19:14 UTC
