Talk:PCC Profile Deprecation
Revision as of 10:22, 22 May 2018 by Tsoutherland (talk | contribs) (Created page with "DCC Call 2018-05-22 === Discussion === * Review PCC Process (not individual profiles for deprecation) * Introduction of new "Intent to Deprecate" status * === Questions ===...")
DCC Call 2018-05-22
Discussion
- Review PCC Process (not individual profiles for deprecation)
- Introduction of new "Intent to Deprecate" status
Questions
- Should the Intent to Deprecate term be set or flexible? What should the term/range of term be?
- "Proposal to Deprecate"
- "Consideration for Deprecation"
- HL7 has used "deprecated" status and standards have been resurrected after community response
- deprecated, retired, removed - understand the definition of each of these
- IHE only has the status of deprecated
- maybe we should add a status of retired
- Deprecated
- Indication that committee has stopped maintenance
- Eligible to move out of deprecated status and back into active status
- Retired
- Deprecation is "final"
- FTP site management considerations
- Identify which existing profiles are deprecated vs retired
- Where in the development cycle would the deprecation process be done?
- value - take advantage of existing marketing channels (i.e. sent out a note along with public comment emails)
- caution against deprecating/intent to deprecate and organizations spending time preparing for connectathon
- How would deprecation/retirement be handled in profiles already published in final text?
- Section headers, start of volume 1 profile add text to highlight deprecation status??
Next Steps
- Propose to adopt these steps across all IHE domains
- PCC: define deprecated and retired, and propose back to DCC
- PCC: identify any PCC specific items and general items and bring back to DCC
- Discuss w/DCC time/term for deprecation