ITI Tech 2007 Meetings

Minutes May 14-18

Attendees

Current Agenda

May_14_18_ITI_Tech_Agenda.V4.doc

DMP Use Case

DMP Use Case 1.0.pdf

Web Services for XDS

Discuss the documents posted at [1]

May 14

• Reviewed open issues in IHE_ITI_TF_Supplement_XDSWS_2007-05-14.doc and resolved all.
• Reviewed XDSWS Option.ppt and agreed to define one chapter in Vol.1 called XDS which describes two profiles - XDS.a (existing set of transactions) XDS.b (new transactions).

Cross-Enterprise User Assertion(XUA)

Issues list at Issues List

Please become familiar with WS-Policy. Two documents are recommended:

• WS-Policy Guidelines document is targeted for new assertion authors (its a work in progress) http://www.w3.org/TR/2007/WD-ws-policy-guidelines-20070330/

• WS-Policy Primer is targeted for policy deplorers http://www.w3.org/TR/2007/WD-ws-policy-primer-20070330/

Cross Community Access (XCA)

Review supplement at XCASupplement.2007.05.10.doc

Background information can be found in April 18-30 online discussion.

PIX/PDQ HL7 V3

Draft of revised supplement is at the IHE ftp site - IHE_ITI_TF_Suppl_PIX-PDQ_HL7v3_TI_2007-05-14.doc

Topics to be discussed:

Volume 1

• New organization as new (separate) profiles
• Naming of the new profiles

Volume 2

General topics:

• Purpose and presentation of the restricted model
• Do we need restricted schema based on the restricted model
• Reference to schema and wsdl files

Patient Identity Feed transaction review

• New organization of the message semantics
• Adding explicit section on specific wrappers
• Wrapper versions

Appendix R

• Data type mapping changes

Retrieve Form for Data-capture (RFD)

Discuss the documents posted at [2]

Latest supplement material is IHE_ITI-TF_Suppl_RFD_TI_2007-05-10.doc

• XForms 1.1
• Security
• updates to Retrieve Form transaction
• new WSDL
• new Retrieve Clarifications transaction

Information on previous tcons can be found at RFD Discussions

Merge/Link Supplement

Draft of the Supplement covering the handling of A40 Merge Patient ID messages in XDS on the FTP site at

xds_patient_link_supp_01.doc

For background on decisions made in this Supplement see the first two entries in the Closed Issues section near the top.

CP Processing

See Change Proposals f2f May 15

Planning for June Conference Speakers

Review latest update on conference schedule, with ITI-sponsored sessions highlighted in yellow, at ihe_workshop_program_v4c.xls

Appendix L updates and XDS National Extensions Guidelines

Revised version of Appendix L revisions based on April 23, 2007 tcon. ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Technical_Cmte/Appendix_L/IHE_ITI_AppendixL_Revisions_v4.0.doc

Most of the revisions have actually been made only to the Terminology and Content sections. Another revised version will be posted just prior to this agenda item.

IHE Security and Privacy for HIE Whitepaper

Review current draft http://wiki.ihe.net/index.php?title=IHE_Security_and_Privacy_for_HIE

Minutes May 2

Attendees - Rob Horn, Bill Majurski, Laurie Williams

Agenda - Configuration Management White Paper

Minutes April 25

Attendees -

Agenda - CP 203 (component/sub-components search in PDQ), 228 (FindDocument SQ eventCode problem), new CP on submitting XDS Associations

Minutes March 30

Attendees Jeff, John, Glen, Roberto, Karen, Lynn, Maryann

See XUA March 30 Agenda and XUA profile.

Discussion topics

• Use and define the term "principal".
• Use case for making privacy (access) decisions. Agree that assertion could be used for access decisions but the profile will not suggest how.
• Trust model, what part of the assertion is trustable
• Be specific regarding which part of standard we are referencing
• Word-smithing and revisions of use case section: See XUA Use Cases for updated use cases.

Minutes March 23

Attendees Karen, Bill, LaVerne, Lynn, Steve, Mike

• CP-ITI-MOORE-PDQ-Connectathon-2007.doc - clarified use of MSH 5&6 and QPD 8. Steve agreed to draw some pictures and add some text to help clarify the point of confusion. Assigned to Steve and # 231.
• CP 225 - suggestion to add a note to each stored queries that uses document uniqueid. This note could refer to the expanded description referenced in the CP
• CP 206 - link vs. merge. Should registry support both merge and link. Current proposal says registry only supports link. Question of what then should it do with a merge message? Conclusion of the attendees is to convert this work into a supplement (spurs greater community comment and allows for a trial implementation period). The supplement would describe solutions for both merge and link. Community comment and trial implementation phase would help refine if both are required.

Minutes March 13-15

Attendees

Attendees List

Web Services for XDS

Reviewed XDSWSv0.7.zip

Issues:

• How to specify the repository id. Repository id is an OID that is globally unique. The issue is how to go from this OID value to connection information. All agree that the submission from the Repository include two elements: Repository unique id and Document unique id. The consumer needs both of these elements to retrieve the document. Concern is that the consumer overhead of converting the repository id to the service endpoint is high.
• obtaining patient id for logging from repository for retrieve. Possible solution is for the client to log the wsa:MessageID for the retrievedocument SOAP transaction
• Should the elements expires/contentType/contentLanguage/lastModified be removed from the document retrieve response. could affect the operation of mapping processes (bridges between old&new) - clarify with Emmanuel. Group agreed to remove these elements.
• consolidate response code across web services (start with reg/rep)

• Structure of the supplement - a lengthy discussion regarding how the transactions would be integrated into the existing XDS profile, or part of a new profile. The product of the discussion is a document which describes a list of choices, one of which will be chosen during the call on April 2.
• The existing stored query requires a very small change to the namespace used. Since the Stored Query is still in Trial Implementation making a small change like this is reasonable and will make the Query transaction consistent with the new transactions.
• Need an IHE namespace policy - Bill agreed to formulate a proposal, distribute it to the ITI and PCC groups and when agreed propose it to the co-chair committee for approval. This supplement will be changed to reflect the outcome of this task. Make URN and not a URL. urn:ihe.net:iti:2007:xds:    is first proposal.

PIX/PDQ HL7 V3 Updates and Web Services Transport

• Content missing from original, will be included this season
• 3 vendors last connectathon
• HL7 version issue, at connectathon the current hl7 version was used. now get document updated
• Newer version of web services binding in hl7 is available - we need to move to it. won't go normative until  w3c and oasis documents stabilize. Concern regarding permanence of spec to support device manufacturers? vassil & roberto believe current effort in hl7 will we stable at end of year except for details like url/urns referenced. Since Trial Implementation version this year we can make small adjustmenet next year to accomadate any changes.
• RMIM - person vs patient - agreed to use patient wherever possible
• Updated doc on PIX/PDQ V3 available in early April.
• The plan is to re-release a public comment version of the supplement in June (at the same time all public comment is released from ITI). And re-release a very different Trial Implementation in August. Expect to go to final text in 2008.

Cross-Enterprise User Assertion(XUA)

See: 3/13/07 XUA Minutes and 3/14/07 XUA Minutes.

Cross Community Access

• Discussion of large volumes of data and significant delay: Agreed that some sort of batching/async was needed. Bill suggested using ebRS "Iterative Query Support". This allows batching of query results. Bill says there is a concern with different types of objects being batched in the return and how they might be mixed. More investigation needed
• Patient ID: Latest doc illustrates the choices. Everyone liked at least one of the options. No resolution.
• Concern with term "Bridge" being confusing: Bridge is a confusing term because it doesn't clearly state that it is inside the organizations (versus between organizations). A new term is desired but was not found in the meeting. How about gateway?
• Bridge chaining: Do we support a bridge propogating requests to another bridge? Proposal by Karen: only if that bridge is "inside" (i.e. invisible to external organizations). The complete implications of this need to be investigated.
• Interactions with XDS Actors: Reviewed flow charts of interactions with XDS registry and XDS repository. Suggested several models for interactions with XDS consumers. Requirement for consumer to be able to request chunks of data, or receive data asynchronously.

XDS Metadata Nation Extensions

Reviewed the French extension to XDS (in French with Charles translating relevent bits). Charles will distribute to a limited group. Small group will work on a checklist for creating a national extension to XDS. Group led by Dave including Sarah, Lori and Charles.

CP Discussion

CP 164: Reviewed xds_164_07.doc. Resolved discussion topics identified in the document. New version to include resolutions and be reviewed in future CP call.

CP 204: Reviewed pix_204_01.doc. A new CP will be created for a related item that came up in the discussion

CP 206: Reviewed xds_206_01.doc.

• Direction is that registry supports link but not merge. This CP will describe how the registry will support link.
• Link will not update metadata but registry will be required to return entries related to all linked patients. Consumer may see patient ids in metadata that is not the same as that queried.
• Suggestion that SQL Query would not support link and if consumer chooses SQL Query they would need to know the linked patient ids and individually query each.

Configuration Management White Paper

Collected problems to be solved relating to web services.

Joint PCC discussion

RFD Data Clarification

Suggestion to rename to notification. Discussion conclusion was that more detail regarding the use case is needed. Further dicussions will address.

Aggregate White Paper and Quality Domain

Charles presented current document

Web Services support of HL7 V3 messages

Discussed schema questions

WS and SOA Work Group

Overview of the ongoing work to create a group which focuses on Web Services and SOA for healthcare. Organizational work ongoing to have this group be a subcommittee of the ITI domain.

HITSP constraints on ITI profiles

• Reviewed XDS constraints and determined they were appropriate as part of a national extension, no updates to XDS
• Began review of PIX/PDQ constraints, continued to call following day. One contraint potentially being submitted as a CP

Future conference calls

Planned furture calls, a list of those scheduled can be accessed here

Minutes February 15

Attendees

Karen, Don, Rob, Adrien, Goerge, Lori, Lynn, Dave, Ellie Avraham, Steve Moore, Roberto, Bill, Eric, Brad, John Moehrke, Steve Speicher

XDS Web Services

Reviewed XDSWSv0.6.zip

• Question if security requires SOAP 1.2? Should both SOAP 1.1 AND SOAP 1.2 be supported or do we require SOAP 1.2 only? Roberto/John to investigate and resolve.
• Be more explicit of list of changes, calling out metadata format changes.
• Discussion of application of security to this profile. Suggestion by John to combine XUA and this work into one supplement - keeping it separate in terms of editing.
• Accessing the repository given only an id, how to find the repository url. Possible ways to dereference the id, UDDI, configuration - need to consider available solutions and identify an appropriate one for this situation
• Question regarding LastModified, could be confusing because explanation suggests document could be modified which XDS does not allow.
• Question of ihe namespace administration - need ihe level procedure. co-chairs need to define procedure.

Cross Community Access

Reviewed XCATechnicalApproach.070214.doc

• Need an ISSUES section: What issues exist around bridge to bridge (likely need to import all text into supplement template)
• Do we need to have an immediate mode transaction, or can an asynchronous and somewhat delayed response be acceptable.
  • Dave is thinking that we may need to have a quality of service built into the request to indicate if this is an emergency/interactive user or is a background task.
  • We want to keep close to current transactions, thus we may need to use synchronous.
  • Still not clear how and to what extent we should need/have/offer asynchronous transactions.
• Discussion around non-patient-specific queries....
• Retrieve - pulls in one transaction all documents requested.
  • Bridge does need to handle one request for documents living in many repositories and affinity domains
  • This is may be an async call
• Security
  • This should include the XUA discussion. Not clear that XUA will function federation-to-federation, through multiple bridges.
• Connection with other IHE profiles (XDS, etc)
  • Update picture to be UML based diagram for end to end interation
  • Discussed approaches to integration with XDS
• Document will be converted to supplement form and discussed at the face-to-face.

Minutes February 6

Attendees

Karen Witting, Larry Wolf, Vassil, Laurie Williams, Goerge Cole, Yongjian Bao, John Carney, Yonaton Maman, Charles Parisot, Kevin Kelly, Don Jorgenson, Lynn, Glen Marshall, Lori, Mark Sinke

Cross Community Access Profile

Reviewed XCATechnicalApproach

Karen will update the document based on the review. Second discussion at next tcon.

Discuss Change Proposals Reviewed CPs can be found at: Assigned

• CP203 Will be discussed at March f2f
• CP212 Charles will write a draft for review
• CP30_06 Charles updated this, we reviewed and it is ready for ballot
• CP227_01 Glen updated this, we reviewed and it is ready for ballot
• CP130_03 We reviewed and is ready for ballot
• CP145_01 We reviewed and is ready for ballot
• CP164 Mark will update and we will review at March f2f
• CP114 Reject
• CP213 First review planned for early April

Incoming Change Proposals

• XDSAuditIssues duplicate of 164
• xds_auto_registration.doc - reject. This CP requested that the registry could support automatic registration of a patient. The group felt that although this is a nice feature to allow it should be configurable and that the testing of XDS would require it be turned off so XDS register transactions specifying an unregistered patient would be rejected. It was stated that some installations would not want this feature so it is imperitive that it be able to be turned off. The request to add support for this into the XDS profile is denied for these reasons.
• rfd_needs_transaction_numbers.doc - assigned 229 and integrate into other RFD changes
• IHE_TF_Change_Proposal-XDS-FindDocumentQuery-eventCode-problem.doc - assigned 228 assigned to Mark
• IHE_TF_Change_Proposal-XDS_SD-softwareName-clarification.doc - assigned 230 consult with Sarah regarding owner

Minutes January 29

Attendees

Karen Witting, Lori, LaVerne, Phillip, Adrian, Roberto, Brad, Kevin, Chad, Lajoie, Yossi, Yonaton, Bill, Rob, Lynn, John, Eli, DAve, Vassil

XDS Web Services

Reviewed WS.zip

XUA Reviewed IHE-Profile-Proposal-Detailed-XUA-20070105.doc

The notes can be found on the XUA page -- meeting notes

Configuration Management Whitepaper

Reviewed Config-Whitepaper-Outline.doc

A google group was created to discuss this white paper. To join go to IHE Configuration Management Whitepaper

Return to ITI Technical Committee