Transport Record Summary Profiles Deprecation
Jump to navigation
Jump to search
Checklist for Assignee for Deprecation
- Answer the questions found in the Evaluation of Published of Profiles
- What is the rationale behind deprecating the Profile?
- Provide specifics as to the need to remove the Profile from publication and for IHE to no longer provide support
- What are the adoption levels of the profile to be deprecated?
- Review Connectathon Test Results page
- Review IHE Product Registry database
- Survey implementers to confirm actual usage in pilot and/or production settings.
- Work with IHE Regional Deployment Domains
- 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?
- What dependencies exist for the Profile being deprecated?
- Are there any required Profile Groupings?
- Are there any dependencies TO other IHE Profiles?
- Are there any dependencies FROM other IHE Profiles?
- Who needs to be notified about deprecating the profile?
- Required groups to be notified: development domain (e.g., PCC), Domain Coordination Committee (DCC).
- Additional groups to be notified: implementers, stakeholders, other IHE Development Domains, IHE Deployment Domains, government organizations
- How long does the Profile remain published in intent to deprecate status?
- The default time period is 18 months
- If a longer or shorter time period is desired, rationale must be provided