pan-canadian hl7 release scope review

Pan-Canadian HL7 ReleaseScope Review

Agenda•Outline the Process used for Prioritizing RFCs

•Discuss the Purpose of this Release

•Provide a Breakdown of RFCs

•Provide Information on How to Access Release Scope on Infocentral

•Outline Process for Commenting on Release Scope

•Describe Future Milestones

•

RFC Assessment

Impact Assessment Considerations

Patient Safety• E.g. Field length not sufficient to display clinical data

Operational Impact• E.g. Design of messages is anticipated to result in system performance challenges once

systems are operational

Development Impact• E.g. Tooling is not supported requiring a manual workaround for software or standards

developers

Impact Assessment

Patient Safety Risk?

OperationRisk?

Develop-ment Risk?

Yes

No

Acceptable solution that can be pre-

adopted

Yes

No

Safety Impact High Impact

Minimal

Yes

Med

Im

pact

Minimal

Acceptable solution that can be pre-

adopted

High Impact

Med

Im

pact

Low

Im

pact

Yes

No

Yes

Priority Assessment

Undergoing Adoption

Commitment to Adopt

Pre-adopted Future Adoption Predicted

No Prediction of Future Adoption

Safety Impact

Urgent Next Release Deferred

High Impact Urgent Next Release Best Efforts Deferred

Med Impact Next Release Best Efforts Deferred

Low Impact Best Efforts Deferred

Purpose of this Release

•Address all RFCs with a priority rating of Urgent or Next Release

•Address RFCs with a priority rating of Best Efforts, where timelines and resources allow

RFC Breakdown

30

** Scope currently includes RFCs from MR2009 and CeRx 4.3

How to Access Release Scope

The Scope of the release has been posted on InfoCentral in the following location:

https://infocentral.infoway-inforoute.ca/2_Standards/1_pan-Canadian_Standards/Z_Open_Review/2013_HL7_Release_Scope_-_For_Public_Comment

This page will include details about how the scope was prioritized, a link to the scope statement and a comment spreadsheet.

Release Scope Statement Spreadsheet• An excel spreadsheet, with a tab for each SCWG

• This spreadsheet includes all open RFCs

• RFCs highlighted in green are currently planned to be included in the next release, and those highlighted in yellow will be included in a best efforts basis

• RFCs that are not highlighted in yellow or green either have a Status of Wait/Under Analysis or the have an SC Priority of Deferred

• Work has been done by the SMEs to summarize both the business and technical requirements

Comment Spreadsheet

• Any Premium Member will have the option to request that an RFC be added or removed from scope

• If an RFC is to be added to the scope of the release, information will need to be provided in the comment spreadsheet about the impact and adoption. The priority of the RFC will then be reassessed by the SC using the matrix displayed in an earlier slide

• If Stakeholders would like to change the technical requirements for an RFC, this should be done through the SCWG during the review period

FAQ1. Can RFCs be added to the scope of the release that

do not yet have their analysis complete? Yes, if the analysis can be completed and the solution approved by the SCWG by February 1st.

2. Can changes be made to the technical requirements of an RFC that is already included in the release scope? Yes, but analysis should be completed and approved by the SCWG by February 1st.

FAQ3. What if there is an RFC that needs to be added to the

scope of the release, but we can’t get the analysis completed by February 1st? If an RFC meets the criteria to be considered an Urgent Priority, it should be brought to the attention of the Release Management team by sending an email to HL7Release@infoway-inforoute.ca

4. What if I would recommend closing an RFC? Bring this to the attention of the responsible SME or send an email to HL7Release@infoway-inforoute.ca, providing your rationale. After the release scope review is complete we will post all RFCs recommended for closure and give Stakeholders an opportunity to comment before closing any RFCs.

Milestone Dates

Milestone Responsible Party

Date Started Date Completed

Draft Scope Statement Published on InfoCentral

SC Dec 10, 2012

Stakeholder Feedback

Stakeholders / SCWGs

Dec 10, 2012 Feb 1, 2013

Feedback Reconciliation

SC Feb 2, 2013 Feb 12, 2013

Approval of Release Scope and Timelines

SCCC Feb 27, 2013 Feb 27, 2013

Questions?