I'm working on cleaning up an outbound XCPD call. As part of my SOAP message that triggers the gateway's outbound XCPD, I'm setting the <device><id> element's @root value to supposedly represent "The application ID(s). IHE restriction: id.root SHALL be an ISO OID, and id.extension SHALL NOT have a value." according to IHE spec.
I need to do this for my Receiver and Sender elements. Here's an example of the Receiver:
For Receiver this would obviously vary partner to partner. I think I've found a way to just specify "unknown".
For Sender (which means "me") I want to use the OID that represents "The CONNECT Gateway". I'm not having an easy time finding what this OID might be. Searching the wiki didn't yield much although it's admittedly difficult to dig through.
Searching hl7.org's registry turned up a handful of results but It's tough to distinguish between testing/specific implementation OIDs meant to represent a gateway and one that's meant to represent the application.
Any pointer appreciated.
(NOTE: I assume that setting a value here would persist through to the XCPD, although a similar post from 2012 mentioned defaulting to the HCID. I haven't verified if this has been fixed or not.)
If I understand you correctly, the Home Community ID can be used interchangeably with the "Device ID" per this spec, is this correct?
Snippet from the bottom of that section reads:
The homeCommunityId is specified as the id element within the Organization associated with
the device of the sender. The id element designating the homeCommunityId shall have only the
845 root element the contents of which is the homeCommunityId.
The spec I was referencing was the (2017) "Wrapper" spec, here:
You can see Application ID mentioned in a few places such as "Table O.1.1-1", all of these are responses to initial queries (so I think the meaning might be handled differently in either direction, or there's a difference due to the age gap of the spec.
Under "Device" there is "ID":
The application ID(s). IHE restriction:
id.root SHALL be an ISO OID, and id.extension SHALL NOT have a value.
And a few extra bits of context:
Optional application brand name
Optional software name
I assumed that the "application ID" was the OID of the actual software given the mention of an optional "software name" but it's not very clear.
Sidebar: does the "Trial" spec govern, or does the newer spec govern?
That's where our understandings diverge. I take the "Device ID" to mean a generic type of product (e.g. the Open Source CONNECT Gateway) not my implementation of that product (e.g. MY gateway, which happens to be the CONNECT open source product, and uses an OID to represent itself).
In the context of cars for example, I'd consider the "Device ID" of a car to be something like "2017 Ford Mustang" and my OID that uniquely identifies the car would be my license plate number like "7ABC123".
To identify WHICH LivingSubjectID element contains the “primary” patient identifier the assigning authority ID corresponds with the assigning authority ID specified
as the id element within the assignedDevice associated with the authorOrPerformer element.
I haven't found any proposals on this that have been adopted so it should be safe to say that the continued use of organization HCID doesn't present a problem. In fact, I would guess that's what's commonly being used now so, for the sake of maintaining interoperability, it might be preferred that users keep using HCID as their device ID. If I recall correctly, there might even be some test tools that would flag you for NOT having your HCID in there, but don't quote me on that.