Minutes Nov 2007 - Sep 2008: Difference between revisions
No edit summary |
No edit summary |
||
| Line 95: | Line 95: | ||
Link to tentative ITI Technical Committee Voting Procedures will be sent to the committee for reviewing. | Link to tentative ITI Technical Committee Voting Procedures will be sent to the committee for reviewing. | ||
<br> | |||
The committee wants to stress that abstention is a perfectly acceptable vote especially when a member didn't have time to review the material subject of the vote before hand. It is reminded that though not counting for assessing whether a proposition is adopted, abstention counts toward quorum and maintaining voting privileges. | <br>The committee wants to stress that abstention is a perfectly acceptable vote especially when a member didn't have time to review the material subject of the vote before hand. It is reminded that though not counting for assessing whether a proposition is adopted, abstention counts toward quorum and maintaining voting privileges. | ||
<br> | |||
Webex is able to handle votes. This possibility will be investigated for T-con voting. | <br>Webex is able to handle votes. This possibility will be investigated for T-con voting. | ||
| Line 105: | Line 105: | ||
Several solid standards could be used for that profile. The detailed proposal has been edited to reflect those standards. | Several solid standards could be used for that profile. The detailed proposal has been edited to reflect those standards. | ||
<br> | |||
It is reminded that each new profile has to include risks assesment and risks mitigation. Any confidentiality issue will be adressed at that point. | <br>It is reminded that each new profile has to include risks assesment and risks mitigation. Any confidentiality issue will be adressed at that point. | ||
<br> | |||
The committee is stressing that Emergency Contact Registry Query profile should be about interoperability and not about how to populate an emergency contact database. | <br>The committee is stressing that Emergency Contact Registry Query profile should be about interoperability and not about how to populate an emergency contact database. | ||
<br> | |||
Though that profile should be small considering the number of pages, it should be assessed as a meidum profile considering the amount of discussion needed to select the right standard. | <br>Though that profile should be small considering the number of pages, it should be assessed as a meidum profile considering the amount of discussion needed to select the right standard. | ||
| Line 117: | Line 117: | ||
In order to keep the profile simple, the scope will be limited to flat value sets. From prospective of profile development the value set shouldn't be limited but for developing and testing purpose the value set used should be an existing one. | In order to keep the profile simple, the scope will be limited to flat value sets. From prospective of profile development the value set shouldn't be limited but for developing and testing purpose the value set used should be an existing one. | ||
<br> | |||
The profile will be based on simple HL7 CTS transactions (a stable and well known standard). | <br>The profile will be based on simple HL7 CTS transactions (a stable and well known standard). | ||
Even though a version 2 of CTS is under development, one of the requirement of CTS 2 is compatibility with CTS. | Even though a version 2 of CTS is under development, one of the requirement of CTS 2 is compatibility with CTS. | ||
<br> | |||
After scoping down, the profile is evaluated as a medium profile. | <br>After scoping down, the profile is evaluated as a medium profile. | ||
===== Cross-Entreprise Service Bus (XSB) ===== | ===== Cross-Entreprise Service Bus (XSB) ===== | ||
| Line 127: | Line 127: | ||
After discussion of the use cases, it has been agreed that the profile be move forth as a white paper. Upon white paper completion, next step will be decided on (depending on the technical scope, it could be as light as a CP to appendix V) | After discussion of the use cases, it has been agreed that the profile be move forth as a white paper. Upon white paper completion, next step will be decided on (depending on the technical scope, it could be as light as a CP to appendix V) | ||
<br> | |||
The white paper should be renamed to better reflect its scope. | <br>The white paper should be renamed to better reflect its scope. | ||
===== Publish/Subscribe Infrastructure for XDS ===== | ===== Publish/Subscribe Infrastructure for XDS ===== | ||
Revision as of 00:56, 8 November 2007
November 7 – 8
Logistics
Location
RSNA Headquarters
820 Jorie Boulevard
Oak Brook, IL 60523
WebEx
To join the WebEx session during the meeting
Go to https://ihe.webex.com/
Conf ID: 920 242 227
Password: meeting
Click on ITI Technical Meeting for today's date
Or follow the instructions to join by teleconference only
Call-in toll-free number (US/Canada): 866-469-3239
Call-in toll number (US/Canada): 650-429-3300
To check for compatibility of rich media players for Universal Communications Format (UCF), click the following link:
https://ihe.webex.com/ihe/systemdiagnosis.php
Nearest Hotel
Marriott Residence Inn
790 Jorie Boulevard
Oak Brook, IL 60523
Ph 630-571-1200
Special Rate: RSNA $139 "subject to availability"
Agenda
The following is a tentative agenda and might be revised during the meeting.
All times are rough estimates and will be changed with little notice.
Links to the detailed proposals that will be discussed during the meeting are given below in the minutes section.
November 7th, Wednesday: 8:30 a.m. to 5:30 p.m.
08:30 (.5) Continental Breakfast
09:00 (.5) Introductions/Agenda Review/Governance discussion
09:30 (2.5) First set :
Emergency Contact Registry Query (ECON)
Sharing Value Sets
Cross-Entreprise Service Bus (XSB)
Publish/Subscribe Infrastructure for XDS
12:00 (1) Lunch
01:00 (1.5) Second set :
Asynchronous XDS.b
Referral Request
Extended PDQ
Update to XDS-SD (Scanned Doc)
to conform to PCC Content Profile template
02:30 (.5) White Papers :
Cross-Community Architecture
Sharing of Terminologies
Policy-Driven Security and Privacy
03:00 (.5) review agenda for next day
03:30 (2) Joint meeting with PCC :
Sharing of Terminology
Referral Request
On-demand queries for XDS
Critical results
Publish/Subscribe Infrastructure for XDS
RFD/QED integration
ECON Query
XDS-SD Update
05:30 Adjourn
November 8th, Thursay: 8:30 a.m. to 3:00 p.m.
08:30 (.5) Continental Breakfast
09:00 (1) CPs critical to connectathon
10:00 (1) White papers from previous years:
Configuration management
Cookbook on security section of IHE Profiles
Template for XDS Affinity Domain Deployment Planning
11:00 (1) Discuss conclusions from discussions
Build consensus for moving forward with lineup of profiles
Consider alternatives to pass on to planning committee
12:00 (1) Lunch
01:00 (1) Vote on lineup of profiles to move forward
02:00 (1) Schedule followup tcons
03:00 Adjourn
Attendees List
Minutes
Governance
Link to tentative ITI Technical Committee Voting Procedures will be sent to the committee for reviewing.
The committee wants to stress that abstention is a perfectly acceptable vote especially when a member didn't have time to review the material subject of the vote before hand. It is reminded that though not counting for assessing whether a proposition is adopted, abstention counts toward quorum and maintaining voting privileges.
Webex is able to handle votes. This possibility will be investigated for T-con voting.
Emergency Contact Registry Query (ECON)
Emergency Contact Registry Query (ECON) detailed proposal
Several solid standards could be used for that profile. The detailed proposal has been edited to reflect those standards.
It is reminded that each new profile has to include risks assesment and risks mitigation. Any confidentiality issue will be adressed at that point.
The committee is stressing that Emergency Contact Registry Query profile should be about interoperability and not about how to populate an emergency contact database.
Though that profile should be small considering the number of pages, it should be assessed as a meidum profile considering the amount of discussion needed to select the right standard.
Sharing Value Sets
Sharing value sets detailed proposal
In order to keep the profile simple, the scope will be limited to flat value sets. From prospective of profile development the value set shouldn't be limited but for developing and testing purpose the value set used should be an existing one.
The profile will be based on simple HL7 CTS transactions (a stable and well known standard).
Even though a version 2 of CTS is under development, one of the requirement of CTS 2 is compatibility with CTS.
After scoping down, the profile is evaluated as a medium profile.
Cross-Entreprise Service Bus (XSB)
Cross-Entreprise Service Bus (XSB) detailed proposal
After discussion of the use cases, it has been agreed that the profile be move forth as a white paper. Upon white paper completion, next step will be decided on (depending on the technical scope, it could be as light as a CP to appendix V)
The white paper should be renamed to better reflect its scope.
Publish/Subscribe Infrastructure for XDS
Publish/Subscribe Infrastructure for XDS detailed proposal
Asynchronous XDS.b
Asynchronous XDS.b detailed proposal
Discussed standards in support of one request and multiple aysnchronous responses. WS-Enumeration may support this but is not a stable standard, only a member submission. Probably will need to scope to one request/one response support until standards are available. Concern that we not create lots of options on the functionality as we adopt newly available standards. Will require evaluation of security in an asynchronous environment. Expected mainly to be a Vol. 1 update to describe the option and Vol. 2 data which refers to WS-I Basic Profile and addresses security concerns. Assessed as Small - 10 pages. Author will be supplied by Microsoft, a name will be provided within the next four weeks.
Referral Request
Referral Request detailed proposal
Extended PDQ
Extended PDQ detailed proposal
White Paper : Cross-Community Architecture
Cross-Community Architecture White Paper detailed proposal
White Paper : Sharing of Terminologies
Terminology Sharing White Paper detailed proposal
White Paper : Policy-Driven Security and Privacy
Joint PCC&ITI Discussion
- Sharing of Terminology
- RFD/QED integration
- Referral Orders
- Critical results
- ECON profile dependencies on PCC profile
- XDS-SD Update to conform to PCC content profile templating
- On-demand queries for XDS
- Publish/Subscribe Infrastructure for XDS
- Patient and Provider communication in the context of medical home and other things
- Consent and family history change - defer to tcon specific for security/privacy
CPs critical to connectathon
See November 8, 2007 CP Minutes.
White papers from previous year
- Configuration management
- Cookbook on security and privacy writing profile
- Template for XDS Affinity Domain Deployment
Conclusion
Vote on lineup of profiles to move forward
Schedule followup tcons
Return to ITI Technical Committee