- Forum
- Communities
- Health Terminologies
- Inactivation of Additional Terminology Subsets from Terminology Gateway (TG)
Inactivation of Additional Terminology Subsets from Terminology Gateway (TG)
- Anil Patel
- Topic Author
- Offline
- Posts: 149
2 months 3 days ago #9732
by Anil Patel
Replied by Anil Patel on topic Inactivation of Additional Terminology Subsets from Terminology Gateway (TG)
Dear HL7 Community,
Some subset owners have requested additional time for analysis before the inactivation occurs. Given there is a need for assessment by stakeholders, the 20th September inactivation will be rescheduled.
Collaboration for Pan-Canadian Subsets: We are open to working with jurisdictions and stakeholders to elevate the value sets to Pan-Canadian status, allowing for broader use across the country. By promoting these subsets, Infoway will maintain oversight, ensuring consistency and accessibility for all implementers:
Clarification on Inactivation: Inactivation of subsets in the Gateway does not mean they will be removed from the Terminology Gateway (TG). They will remain accessible for reference until the Terminology Gateway (TG) is decommissioned, but will be marked as inactive, signaling that they should no longer be used for new implementations.
We are aware of the concerns raised and are working to ensure that these concerns are addressed as part of the updated plan. We remain committed to collaborating with stakeholders to find solutions that minimize disruption and maintain access to critical value sets.
We encourage stakeholders to reach out if they wish to discuss the possibility of promoting specific value sets.
Best regards,
Anil Patel
Some subset owners have requested additional time for analysis before the inactivation occurs. Given there is a need for assessment by stakeholders, the 20th September inactivation will be rescheduled.
Collaboration for Pan-Canadian Subsets: We are open to working with jurisdictions and stakeholders to elevate the value sets to Pan-Canadian status, allowing for broader use across the country. By promoting these subsets, Infoway will maintain oversight, ensuring consistency and accessibility for all implementers:
Clarification on Inactivation: Inactivation of subsets in the Gateway does not mean they will be removed from the Terminology Gateway (TG). They will remain accessible for reference until the Terminology Gateway (TG) is decommissioned, but will be marked as inactive, signaling that they should no longer be used for new implementations.
We are aware of the concerns raised and are working to ensure that these concerns are addressed as part of the updated plan. We remain committed to collaborating with stakeholders to find solutions that minimize disruption and maintain access to critical value sets.
We encourage stakeholders to reach out if they wish to discuss the possibility of promoting specific value sets.
Best regards,
Anil Patel
Please Log in or Create an account to join the conversation.
- Anil Patel
- Topic Author
- Offline
- Posts: 149
2 months 1 week ago #9713
by Anil Patel
Replied by Anil Patel on topic Inactivation of Additional Terminology Subsets from Terminology Gateway (TG)
Hi Sheridan,
Thank you for outlining the current state of the practitionerSpecialty ValueSet in the CA Baseline PractitionerRole profile. After reviewing your concerns, we propose to keep the practitionerSpecialty ValueSet active for the time being.
As you mentioned, PS-ON and PS-CA reference this ValueSet, with BC using a related SCPQual ValueSet.
We will have internal discussions at Infoway regarding this subset and will consult with the relevant stakeholders. Please let us know if you support this approach or if there are any other factors we should take into account during the decision-making process
Anil
Thank you for outlining the current state of the practitionerSpecialty ValueSet in the CA Baseline PractitionerRole profile. After reviewing your concerns, we propose to keep the practitionerSpecialty ValueSet active for the time being.
As you mentioned, PS-ON and PS-CA reference this ValueSet, with BC using a related SCPQual ValueSet.
We will have internal discussions at Infoway regarding this subset and will consult with the relevant stakeholders. Please let us know if you support this approach or if there are any other factors we should take into account during the decision-making process
Anil
Please Log in or Create an account to join the conversation.
- Sheridan Cook
- Offline
- Posts: 68
2 months 2 weeks ago #9698
by Sheridan Cook
Replied by Sheridan Cook on topic Inactivation of Additional Terminology Subsets from Terminology Gateway (TG)
We are currently utilizing practitionerSpecialty (fhir.infoway-inforoute.ca/ValueSet/practitionerspecialty) in the CA baseline PractitionerRole profile, Additionally:
PS-ON uses this in PractitionerRole, PS-CA also uses this by merit of pointing to CA Baseline profiles for Practitioner and PractitionerRole
BC the practitionerRole uses the SCPQual valueSet unioned from local codes
Others there isn’t definitive evidence in other specs that it’s being used or not used (e.g., eReferral, AB, elsewhere) but this isn’t indicative that it’s not in use
Based on how the CA Baseline uses the valueSet (in a stub) removal from TG without replacing via some other means (e.g., Terminology Server) would mean that our link for viewers to look at the valueSet would no longer work(will still be viewable), and that the canonical url that currently allows users of the baseline to hit the FHIR API of TG and receive a download of the ValueSet, would also no longer work (assuming)
While we can technically still include the canonical url as our binding (even if its content no longer is resolvable/findable on the internet, or if it would require re-routing/mapping to new valueSets)
We are also concerned that inactivation constitutes a message that it is no longer valid for use, meaning the CA Baseline would have to identify an alternative
We are proposing the following: 1) maintain it as an active ValueSet that makes the transition to the Terminology Server, 2) An alternative is identified (through some mechanism) before it is inactivated to avoid disruption as an end user
Should we be concerned that there is the possibility that the presence in Baseline & PS-CA/PS-ON, without confirmation jurisdictions are using, that it would mean it is just being kept alive because of it showing up on profiling artefacts?
PS-ON uses this in PractitionerRole, PS-CA also uses this by merit of pointing to CA Baseline profiles for Practitioner and PractitionerRole
BC the practitionerRole uses the SCPQual valueSet unioned from local codes
Others there isn’t definitive evidence in other specs that it’s being used or not used (e.g., eReferral, AB, elsewhere) but this isn’t indicative that it’s not in use
Based on how the CA Baseline uses the valueSet (in a stub) removal from TG without replacing via some other means (e.g., Terminology Server) would mean that our link for viewers to look at the valueSet would no longer work(will still be viewable), and that the canonical url that currently allows users of the baseline to hit the FHIR API of TG and receive a download of the ValueSet, would also no longer work (assuming)
While we can technically still include the canonical url as our binding (even if its content no longer is resolvable/findable on the internet, or if it would require re-routing/mapping to new valueSets)
We are also concerned that inactivation constitutes a message that it is no longer valid for use, meaning the CA Baseline would have to identify an alternative
We are proposing the following: 1) maintain it as an active ValueSet that makes the transition to the Terminology Server, 2) An alternative is identified (through some mechanism) before it is inactivated to avoid disruption as an end user
Should we be concerned that there is the possibility that the presence in Baseline & PS-CA/PS-ON, without confirmation jurisdictions are using, that it would mean it is just being kept alive because of it showing up on profiling artefacts?
Please Log in or Create an account to join the conversation.
- Anil Patel
- Topic Author
- Offline
- Posts: 149
2 months 2 weeks ago #9680
by Anil Patel
Inactivation of Additional Terminology Subsets from Terminology Gateway (TG) was created by Anil Patel
Hi HTC Members,
As part of the decommissioning of the Terminology Gateway (TG), we would like to inform you that additional terminology subsets will be deactivated on September 20th. This decision has been communicated to the affected stakeholders, and we will be moving forward with the inactivation of these subsets.
Below is the list of Additional Terminology Subsets that have been agreed upon for inactivation:
URLCatalog
HttpResponseStatusCode
CommunicableDiseaseCausativeAgentCode
CommunicableDiseaseStageCode
CommunicableDiseasePresentationCode
FavouritedEMRCodes
PrescriptionODBReasonForUse
PractitionerSpecialty
MedicationDispenseCategory
DrugSubClassification
ConsentPersonalRelationship
DrugDosageFormAbbreviations
DrugClassification
DURInterventionException
IconImmunizationSubmissionVaccineCode
IconImmunizationRetrievalVaccineCode
IconImmunizationRecommendationVaccineCode
ImmunizationRouteOfAdministration
CanadianTriageAcuityScale
DURResponseCodes
AacAdmitCategory (CIHI)
CanadianTriageAcuityScale (CIHI)
Please note that this inactivation is aligned with our ongoing efforts to streamline our terminology services and ensure that the new Terminology Server (TS) supports only Pan-Canadian Value Sets.
If you have any questions or require further information, please contact us.
Thank you for your understanding and continued collaboration.
Best regards,
Anil
As part of the decommissioning of the Terminology Gateway (TG), we would like to inform you that additional terminology subsets will be deactivated on September 20th. This decision has been communicated to the affected stakeholders, and we will be moving forward with the inactivation of these subsets.
Below is the list of Additional Terminology Subsets that have been agreed upon for inactivation:
URLCatalog
HttpResponseStatusCode
CommunicableDiseaseCausativeAgentCode
CommunicableDiseaseStageCode
CommunicableDiseasePresentationCode
FavouritedEMRCodes
PrescriptionODBReasonForUse
PractitionerSpecialty
MedicationDispenseCategory
DrugSubClassification
ConsentPersonalRelationship
DrugDosageFormAbbreviations
DrugClassification
DURInterventionException
IconImmunizationSubmissionVaccineCode
IconImmunizationRetrievalVaccineCode
IconImmunizationRecommendationVaccineCode
ImmunizationRouteOfAdministration
CanadianTriageAcuityScale
DURResponseCodes
AacAdmitCategory (CIHI)
CanadianTriageAcuityScale (CIHI)
Please note that this inactivation is aligned with our ongoing efforts to streamline our terminology services and ensure that the new Terminology Server (TS) supports only Pan-Canadian Value Sets.
If you have any questions or require further information, please contact us.
Thank you for your understanding and continued collaboration.
Best regards,
Anil
Please Log in or Create an account to join the conversation.