ITI Planning 26Oct07 Notes

ITI Planning Committee - Minutes 26Oct07

Purpose - to review detailed profile and white paper proposals in preparation for submission to ITI Technical Committee.

Asynch XDS.B

Roberto will ensure another editor from Microsoft is assigned. The Wiki page will be updated. Use Case #1 - Roberto will strenthen this scenario and move it lower in the document, as it is lower priority. Scenario 2, 3 & 4 are most compelling. Scenario 3, change to "slow archive".

Add that this profile WILL apply to XCA transactions (describe in technical approach).

How about XDR - add to open issues? Technical Committee to review.

Referral Request

Rob Horn is likely to be editor... will confirm by November.

Add that PCC has a keen interest in this proposal. Suggest we update the template to add a section on interaction with other domains.

Open issues: Planning Committee decisions required. After TC Review, will transmit discussion to PC for any additional resolution.

Sharing Value Sets

Profile proposal is very long and detailed. Suggest summarizing at a higher level. Use cass should be written as a health care storyboard.

ITI Tech can't undertake 7 new transactions... suggest 2 or 3 for year 1 work.

Simplify transactions (down to 2) and describe actors at PC level.

Scott (Mayo) has parallel work being undertaken over the next couple of years.

Extended PDQ Detailed Profile Proposal

New profile or change proposal? Connections between the summary and technical approach. Remove those functions that don't change functionallity and resubmit as a CP. New function (adding of extra fields) to remain. Karen W. will draft CP for Alean, and will seek validation.

Cross-Enterprise Service Bus (XSB)

Don Jorgenson not present.

Proposal should be renamed... something that includes security and privacy.

Committee is struggling to find the "work" in this proposal... is this really a proposal or more appendix work? Is this a document supplement, or a technical commitee white paper?

Suggest author remove the word "profile" after XSB, submit to TC for discussion and determination as to the appropriate format.

Original intent was to profile content of security and privacy elements in web services transactions. This proposal needs to be re-written to reflect original intent. Charles to communicate this back to Don.

ECON Query Profile

Technical Committee to evaluate whether this proposal is better suited as a TC.

Publish/Subscribe Infrastructure for XDS

Risk section needs to be completed prior to Technical Committee. (1) Continuity of Trust; (2) Scope of solution too broad? To be discussed at TC.

Is this a re-use of NAV? To be assessed at TC.

Connection with Asynch XDS.b, define and document in both proposals.

White Papers

Cross-Community Architecture White Paper

Committee is comfortable with the scope and detail of the proposal as it exists.

Add that this is to be a TC white paper with technical content. Mick Talley to assist. mtalley@university-bank.com.

Expecting enough detail to allow potential implementers (NHIN2 contractors) to see value as potential beneficiaries and to provide usable feedback.

Terminology Sharing White Paper

More precision to define scope of this white paper. Suggest constraining Use Case 3 to existing value sets from already defined terminologies.

Policy-Driven Security and Privacy

No use case about navigating a relational (hierarchical) terminology. Authors will add to use case 3.