Difference between revisions of "PCC Profile Deprecation Process"
Jump to navigation
Jump to search
Tsoutherland (talk | contribs) |
Tsoutherland (talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | = Overview = | ||
From time to time IHE Profiles need to be deprecated for one reason or another. As there is no formal IHE process for this each domain is free to determine what actions need to be taken in order to deprecate a profile in their domain. This page outlines the process for PCC. | From time to time IHE Profiles need to be deprecated for one reason or another. As there is no formal IHE process for this each domain is free to determine what actions need to be taken in order to deprecate a profile in their domain. This page outlines the process for PCC. | ||
In order to deprecate a profile, an assessment must be performed to determine the community impact of the deprecation. If this assessment is not performed then there could be negative impact, causing disruption in interoperability implementations as vendors, policy-makers, and other stakeholders may decide to cease support for a profile based on deprecation status. | In order to deprecate a profile, an assessment must be performed to determine the community impact of the deprecation. If this assessment is not performed then there could be negative impact, causing disruption in interoperability implementations as vendors, policy-makers, and other stakeholders may decide to cease support for a profile based on deprecation status. | ||
| + | = Process = | ||
Following are a list of questions to ask, and suggested actions to take. | Following are a list of questions to ask, and suggested actions to take. | ||
| Line 15: | Line 17: | ||
| + | = Questions and Discussion = | ||
| − | |||
* Where should answers to the above questions be documented? On the wiki? In a Google document? Elsewhere? | * Where should answers to the above questions be documented? On the wiki? In a Google document? Elsewhere? | ||
* Should we specify a time limit for deprecation? i.e. a profile will remain in deprecated state for a period of 6 months, and then be removed from the wiki, ihe.net website, etc. | * Should we specify a time limit for deprecation? i.e. a profile will remain in deprecated state for a period of 6 months, and then be removed from the wiki, ihe.net website, etc. | ||
Revision as of 06:07, 12 February 2018
Overview
From time to time IHE Profiles need to be deprecated for one reason or another. As there is no formal IHE process for this each domain is free to determine what actions need to be taken in order to deprecate a profile in their domain. This page outlines the process for PCC.
In order to deprecate a profile, an assessment must be performed to determine the community impact of the deprecation. If this assessment is not performed then there could be negative impact, causing disruption in interoperability implementations as vendors, policy-makers, and other stakeholders may decide to cease support for a profile based on deprecation status.
Process
Following are a list of questions to ask, and suggested actions to take.
- What are the adoption levels of the profile to be deprecated?
- Review Connectathon Test Results page.
- Review IHE Product Registry database.
- If appropriate, survey implementers to confirm actual usage in pilot and/or production settings.
- Is the profile being deprecated being replaced by a new profile?
- If yes, which profile, and what actors, transactions, options, etc. are being used in the new profile?
- Who needs to be notified about deprecating the profile?
- Consider implementers and stakeholders, other IHE Domains, any government organizations
Questions and Discussion
- Where should answers to the above questions be documented? On the wiki? In a Google document? Elsewhere?
- Should we specify a time limit for deprecation? i.e. a profile will remain in deprecated state for a period of 6 months, and then be removed from the wiki, ihe.net website, etc.