Difference between revisions of "ITI Planning 26Oct07 Notes"
m |
m |
||
| Line 1: | Line 1: | ||
| − | + | ==ITI Planning Committee - Minutes 26Oct07== | |
Purpose - to review detailed profile and white paper proposals in preparation for submission to ITI Technical Committee. | Purpose - to review detailed profile and white paper proposals in preparation for submission to ITI Technical Committee. | ||
| − | ==Asynch XDS.B== | + | ===Asynch XDS.B=== |
Roberto will ensure another editor from Microsoft is assigned. The Wiki page will be updated. | 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". | 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". | ||
| Line 10: | Line 10: | ||
How about XDR - add to open issues? Technical Committee to review. | How about XDR - add to open issues? Technical Committee to review. | ||
| − | ==Referral Request== | + | ===Referral Request=== |
Rob Horn is likely to be editor... will confirm by November. | Rob Horn is likely to be editor... will confirm by November. | ||
| Line 17: | Line 17: | ||
Open issues: Planning Committee decisions required. After TC Review, will transmit discussion to PC for any additional resolution. | Open issues: Planning Committee decisions required. After TC Review, will transmit discussion to PC for any additional resolution. | ||
| − | ==Sharing Value Sets== | + | ===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. | Profile proposal is very long and detailed. Suggest summarizing at a higher level. Use cass should be written as a health care storyboard. | ||
| Line 26: | Line 26: | ||
Scott (Mayo) has parallel work being undertaken over the next couple of years. | Scott (Mayo) has parallel work being undertaken over the next couple of years. | ||
| − | ==Extended PDQ Detailed Profile Proposal== | + | ===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)== | + | ===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. | |
| − | == | + | ===ECON Query Profile=== |
| − | ==Terminology Sharing White Paper== | + | |
| + | ==White Papers== | ||
| + | |||
| + | ===Cross-Community Architecture White Paper=== | ||
| + | |||
| + | ===Terminology Sharing White Paper=== | ||
Revision as of 11:59, 26 October 2007
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.