-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Abandonment process for old TI supplements #170
Comments
should pick up in the spring |
Definitely good to record a rationale for deprecation. |
We do use that process. This item is not to write a process, it is to
execute the existing process across the portfolio.
John Moehrke - Architect: Standards - Interoperability, Privacy, and
Security for Bylight.com
https://healthcaresecprivacy.blogspot.com
…On Mon, Jun 20, 2022, 12:38 PM kevino7 ***@***.***> wrote:
Definitely good to record a rationale for deprecation.
Should harmonize with the existing process:
https://wiki.ihe.net/index.php/Evaluation_of_Published_Profiles
If needed can expand the deprecation reasons to include "Boredom/Apathy"
:-)
—
Reply to this email directly, view it on GitHub
<#170 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHBWC5ZMVVWLNY5XNKAHFLDVQCT7ZANCNFSM5CKGYNTQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: