Example Scenario #1:

convertingtownSoftware and s/w Development

Nov 4, 2013 (3 years and 11 months ago)

75 views


Example Scenario

#1
:

For the trial implementations in November 2009, ONC sponsored the AHIC Emergency Responder Use
Case.


Integration Profile:

Emergency Responder v1.0

Integration Profile
URN
designator
:

urn:nhin:onc:emergency
-
responder:1.0


The
selected specifications for this Integration Profile:

Specification

Version

Messaging Platform

1.9.1

Authorization Framework

1.9.1

Subject Discovery

1.9.4

Query for Documents

1.6.8

Retrieve Documents

1.6.6



Integration Profile Participants:

There are two participants in this profile.

Participant

Description

Initiator

This identifies the participant that will initiate the sequence of transactions,
and act as the client for each of the selected transactions.

Responder

his identifies the par
ticipate that will respond to those transactions.


The Integration profile designators would be:

Participant

Description

Initiator

urn:nhin:onc:emergency
-
responder:1.0:Initiator

Responder

urn:nhin:onc:emergency
-
responder:1.0:Responder





Integration Profile
Transaction Designators
:

Transaction Name

(based on spec)

Transaction Designator

Subject Discovery

urn:nhin:onc:emergency
-
responder:1.0:Responder:SubjectDiscovery:1.9

Query For Documents

urn:nhin:onc:emergency
-
responder:1.0:Responder:QueryForDocuments:1.6

Retrieve Documents

urn:nhin:onc:emergency
-
responder:1.0:Responder:RetrieveDocuments:1.6


At this point, the three transactions are bound to both the Messaging Platform and Authorization

Framework specifications. As a reminder, for the Trial Implementations in 2009, the Messaging Platform
specification was based on SOAP 1.1.


The last step in the process would be to register the actual service endpoints for a home community,
into the Ser
vice Registry using the transaction designator as the key, where the value returned would be
the URL to the service.



Example

Service Registry endpoints for HIE #1
:


urn:nhin:onc:emergency
-
responder:1.0:Responder:SubjectDiscovery:1.9

https://web
-
service.h
ie1.com/nhin/SubjectDiscovery


urn:nhin:onc:emergency
-
responder:1.0:Responder:QueryForDocuments:1.6

https://web
-
service.hie1.com/nhin/QueryForDocuments


urn:nhin:onc:emergency
-
responder:1.0:Responder:RetrieveDocuments:1.6

https://web
-
service.hie1.com/nhin/RetrieveDocuments





Example Scenario #2:

In February 2010, as part of the preparation to move to a Production NHIN, ONC updates the Emergency
Responder Integration profile, to adopt the production specifications that were release in February
2010. Additionally, ONC decided to rebrand the origina
l NHIN and call it NHIN Echange


The integration profile version number is updated to 2.0


Integration Profile:

Emergency Responder v2.0

Integration Profile URN designator:

urn:nhin
-
exchange:onc:emergency
-
responder:2.0


Additionally, the selected specif
ications list is also updated:

Specification

Version

Messaging Platform

2.0

Authorization Framework

2.0

Patient Discovery

1.0

Query for Documents

2.0

Retrieve Documents

2.0



Integration Profile Participants:

There are two participants in this profile.

Participant

Description

Initiator

This identifies the participant that will initiate the sequence of transactions,
and act as the client for each of the selected transactions.

Responder

his

identifies the participate that will respond to those transactions.


The Integration profile designators would be:

Participant

Description

Initiator

urn:nhin
-
exchange:onc:emergency
-
responder:2.0:Initiator

Responder

urn:nhin
-
exchange:onc:emergency
-
respo
nder:2.0:Responder





Integration Profile
Transaction Designators
:

Transaction
Name

(based on
spec)

Transaction Designator

Patient
Discovery

urn:nhin
-
exchange:onc:emergency
-
responder:2.0:Responder:PatientDiscovery:1.0

Query For
Documents

urn:nhin
-
exchange
:onc:emergency
-
responder:2.0:Responder:QueryForDocuments:2.0

Retrieve
Documents

urn:nhin
-
exchange
:onc:emergency
-
responder:2.0:Responder:RetrieveDocuments:2.0


At this point, the three transactions are bound to version 2 of the Messaging Platform

and Authorization
Framework specifications. As a reminder, In February 2010, the Messaging Platform specification was
based on SOAP 1.2.



Example Service Registry endpoints for HIE #1 for version 2 of the
Emergency Responder Integration
Profile
:


urn:
nhin:onc:emergency
-
responder:2.0:Responder:PatientDiscovery:1.0

https://web
-
service.hie1.com/nhin
-
exchange/PatientDiscovery


urn:nhin:onc:emergency
-
responder:1.0:Responder:QueryForDocuments:2.0

https://web
-
service.hie1.com/nhin
-
exchange/QueryForDocuments


urn:nhin:onc:emergency
-
responder:1.0:Responder:RetrieveDocuments:2.0

https://web
-
service.hie1.com/nhin
-
exchange/RetrieveDocuments

As an example of how this enables versioning and migration support for the NHIN:

Fictitious HIE #1 used the v1.0 specification

to perform a limited production interchange with another
partner HIE #2. HIE #2 does not have the resources to upgrade to the latest version at this time.
However, HIE #1 still wants to migrate to the latest version. Using the above approach, both sets

of
integration endpoints can be registered into the service registry without any conflict.


Final Service Registry Entry values for HIE #1:

(Supporting Emergency Responder v1)

urn:nhin:onc:emergency
-
responder:1.0:Responder:SubjectDiscovery:1.9

https://we
b
-
service.hie1.com/nhin/SubjectDiscovery


urn:nhin:onc:emergency
-
responder:1.0:Responder:QueryForDocuments:1.6

https://web
-
service.hie1.com/nhin/QueryForDocuments


urn:nhin:onc:emergency
-
responder:1.0:Responder:RetrieveDocuments:1.6

https://web
-
service.hie
1.com/nhin/RetrieveDocuments


(Supporting Emergency Responder v2)

urn:nhin:onc:emergency
-
responder:2.0:Responder:PatientDiscovery:1.0

https://web
-
service.hie1.com/nhin
-
exchange/PatientDiscovery


urn:nhin:onc:emergency
-
responder:1.0:Responder:QueryForDocume
nts:2.0

https://web
-
service.hie1.com/nhin
-
exchange/QueryForDocuments


urn:nhin:onc:emergency
-
responder:1.0:Responder:RetrieveDocuments:2.0

https://web
-
service.hie1.com/nhin
-
exchange/RetrieveDocuments