ITI CP Ballot 64 - Submit your comments by Monday, September 16

[Bell, Sarah]

Greetings IHE ITI Technical, ITI Planning, and Domain Coordination Committee members:

 

The IT Infrastructure Technical Committee is accepting votes and comments on Ballot #64 Change Proposals (CPs) for IT Infrastructure domain profiles.

Timeline:  Ballot is open from today, August 16, 2024, through Monday, September 16, 2024

Submitting Comments/Votes:  

• Submit your comments/votes in this google doc
• OR you may use the spreadsheet in the attached zip file to compile your votes and comments.  Submit the completed spreadsheet to ITI Comments mailing list (itico...@googlegroups.com). 

 

Voting Rights Reminder: Casting your vote and providing comments on CP ballots is a great way to maintain your organization’s voting rights! Make sure your voting rights stay active by participating in CP ballots! 

 

Ballot contents:  The CPs listed below and the comment spreadsheet are in the attached zip file and in IHE Documents in Google Drive which can be found here. 

 

CP-ITI	Title	Ballot Result
1284-02	XDS: Clarify XDSRepositoryOutOfResources vs. XDSTooManyResults semantics in the context of a retrieve
1285-03	XUA: Add Audience SAML Errata Guidance
1292-01	Align IHE ITI with ELGA - homeCommunityID
1294-00	Clarify XDS Associations Have EntryUUID Sources and Targets
1296-00	Requirement on Actors to support all events incorrect
1298-00	Clarify XDS Metadata maximum length
1299-00	Inconsistency of homeCommunityId length
1300-00	DSG XML improvements
1301-03	Parameter homeCommunityId in [ITI-18] with patient id
1302-00	Fix namespace URI in entity-type search parameter
1304-00	XCPD Add Query Targeting
1314-01	$match output Parameters profile

 

 

 

Thank you!

 

Sarah Bell, MA

She/Her Pronouns

Program Manager, Informatics

T  312.915.9524  |  E  sarah...@himss.org

 

[John Moehrke]

Reminder to ITI committee members to review and comment/vote on this CP ballot. There are significant CPs in this ballot. Reminder that voting on CP ballots is a membership task.

--
You received this message because you are subscribed to the Google Groups "IHE Domain Coordination Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcc+uns...@ihe.net.
To view this discussion on the web visit https://groups.google.com/a/ihe.net/d/msgid/dcc/SJ0PR11MB4895010CC6F26B2D4A788CEA82812%40SJ0PR11MB4895.namprd11.prod.outlook.com.

[Bell, Sarah]

Greetings IHE ITI Technical, ITI Planning, and Domain Coordination Committee members:

 

One week left to submit your votes and comments on ITI CP Ballot 64!

[Andries Hamster]

Dear Spencer, et. al.

Going through the list of CPs I noticed CP-ITI-1304-00 (XCPD Add Query Targeting).

I am in favour of expanding the XCPD profile with support to "target" are remote community. However, I am not entire convinced that the proposed change will work in the "real world" as it makes an explicit assumption that the responding XCPD gateway is acting as a proxy to multiple homeCommunities, returning an aggregated response from multiple communities that discover that patient.

As an initiating XCPD gateway queries by patient demographics mostly to discover the existence of the same patient in a remote community, the burden is upon the initiating XCDP gateway to filter from the aggregated response the patient entries of interest. When using a responding gateway acting as a proxy this aggregated response may be quite overwhelming.

Furthermore, the need for "targeting" a specific community may come from the fact that, as a initiating gateway I don't want to broadcast my query (perhaps because some countries legally prohibit that) to many communities I am not interested in. I would argue that the need to target comes from either a human user that knows what community/ies to query. Or from some prior or external knowledge the initiating gateway has before it issues an ITI-55 transaction.

Although suggested in some of the described use-cases the XCPD profile does not define what triggers an ITI-55 transaction. This trigger may be, as suggested in the profile, a patient identity feed, or an ITI-18 transaction. However, there not such thing as a PDQ query from a consumer application that is captured by a initiating XCDP gateway, like what ITI-18 is to an Initiating XCA gateway. So, if we would add a targeting option to XCPD I firstly would like to suggest we discuss how to bring the information about which communities to target to an initiating XCDP gateway.

I would suggest that we should look at grouping PDQ and XCPD. Doing so gives a user the ability to issue a PDQ query indicating what communities to target, in combination with the "what domains return" attribute. The initiating XCPD gateway can evaluate the PDQ query parameters and use it to target specific responding XCDP gateways. From the response it receives it filters for entries that match the "what domains returned" list.

Hence, it would be great if we can add a new (optional) transaction like ITI-18 for the XCDP profile, allowing a "consumer" type actor to send a request to its initiating gateway to target a XCPD query. Or we can re-use a PDQ query transaction and add a "targetCommunityIdList" attribute similar to CP 1301-03

I hope I have expressed my concerns to the propose change in the profile well enough. Open for further discussion.

Best regards,

Andries Hamster

--
You received this message because you are subscribed to the Google Groups "IHE ITI Technical Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ititech+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ititech/SJ0PR11MB489545CBC9093AB755EBEBDE82992%40SJ0PR11MB4895.namprd11.prod.outlook.com.

[Spencer LaGesse]

Andries,

Thanks for the input. I am confident that CP 1304-00 will work for at least my use case, since in my use case my XCPD Initiating Gateway is triggered from internal triggers, some of which occur with direct user input. And of course an Initiating Gateway might be triggered by a grouped XCPD Responding Gateway, which would of course work with this solution. 

I actually think this also pairs quite nicely with the standard XDS architecture as well. If a Document Consumer wants to search for documents in a particular community, they would:

- Issue a PDQ query to the local Patient Identity Source to get the patient's ID within the local XDS affinity domain

- Issue an ITI-18 transaction to the local Initiating Gateway specifying the patient's local affinity domain identifier, and also specifying the target community using the capabilities added by CP-ITI-1303. 

- The Initiating Gateway is responsible for translating the patient identifier to the one known by the responding community. It is responsible for discovering the patient's remote ID, potentially by using the new capability proposed for XCPD. 

- The Initiating Gateway sends the ITI-38 query using the ID for the remote community

- The response is returned to the Document Consumer

The ability to translate a patient ID from the local affinity domain identifier to the remote community identifier is listed as a responsibility of the Initiating Gateway supporting the XDS Affinity Domain Option in ITI TF-1 18.2.1.

I suspect that this is why there is no "XDS Affinity Domain Option" in XCPD. The expectation is that for patient discovery, local actors need only to know the local affinity domain ID, and the Initiating Gateway will be responsible for translating as needed. 

So, while I am not opposed to adding the concept of home community ID to one or more of the PDQ flavors, I don't think it needs to be done by this CP, but should instead be a separate CP or work item. 

Thanks,

Spencer

[Bell, Sarah]

Greetings IHE ITI Technical, ITI Planning, and Domain Coordination Committee members:

 

The IT Infrastructure Technical Committee is accepting votes and comments on Ballot #65 Change Proposals (CPs) for IT Infrastructure domain profiles.

Timeline:  Ballot is open from today, May 7, 2025 through Friday June 6, 2025

Submitting Comments/Votes:  

• Submit your comments/votes in this google doc
• OR you may use the spreadsheet in the attached zip file to compile your votes and comments.  Submit the completed spreadsheet to ITI Comments mailing list (itico...@googlegroups.com). 

 

Voting Rights Reminder: Casting your vote and providing comments on CP ballots is a great way to maintain your organization’s voting rights! Make sure your voting rights stay active by participating in CP ballots! 

 

Ballot contents:  The CPs listed below and the comment spreadsheet are in the attached zip file and in IHE Documents in Google Drive which can be found here. 

 

CP-ITI	Title	Ballot Result
1255-04	ihe_iua extension example does not conform to text? #75
1295-03	Conflicting requirement on support for UDP and TLS for the Audit Record Repository
1297-09	Transaction updates for Sex and Gender Encoding
1306-03	Missing Definition of “request”
1317-00	oraganizationDirectory spelling mistake found in CSD Profile
1319-00	Clarify Notify Message triggers in [ITI-54]
1320-02	Incorrect JSON example in RESTful ATNA
1321-01	CX clarification in XUA
1322-03	XCA federation of MHDS community

[John Moehrke]

Reminder ITI members to review and vote on this CP ballot. 

John Moehrke 🔥 Architect: Healthcare Informatics Standards - Interoperability, Privacy, and Security
IHE Co-Chair IT Infrastructure Planning and Technical
HL7 Co-Chair Security WG, FHIR FMG, FHIR facilitator, and FHIR Foundation founding member

Employee of By Light -- Contractor to VHA MyHealtheVet
JohnM...@gmail.com  |  M +1 920-564-2067  |  John.M...@bylight.com
 https://healthcaresecprivacy.blogspot.com

--

You received this message because you are subscribed to the Google Groups "IHE Domain Coordination Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcc+uns...@ihe.net.

To view this discussion visit https://groups.google.com/a/ihe.net/d/msgid/dcc/SJ0PR11MB48950EC27C8BD5428A15D3978288A%40SJ0PR11MB4895.namprd11.prod.outlook.com.

[Bell, Sarah]