June 28-29, 2005IHE Interoperability Workshop Keith W. Boone Dictaphone Corporation IHE ITI Technical Comittee Notification of Document Availability (NAV)

June 28-29, 2005 IHE Interoperability Workshop

Keith W. BooneDictaphone Corporation

IHE ITI Technical Comittee

Notification of Document Availability(NAV)

Notification of Document Availability(NAV)

June 28-29, 2005 IHE Interoperability Workshop2

W W W . I H E . N E TW W W . I H E . N E T

Providers and VendorsWorking Together to Deliver

Interoperable Health Information SystemsIn the Enterprise

and Across Care Settings


Notification of Document Availability Notification of Document Availability AbstractAbstract

Existing e-mail systems are employed to notify users of document availability in an XDS Affinity Domain.


Register DocumentsRegister Documents

XDS Document RepositoryXDS Document Repository XDS Document RegistryXDS Document Registry

Query RegistryQuery Registry

XDS Document ConsumerXDS Document Consumer

Provide and Provide and Register DocumentsRegister Documents

XDS Document SourceXDS Document Source

Retrieve DocumentsRetrieve Documents

Notification of Document Availability Notification of Document Availability ScopeScope

It doesn’t get much simpler than this…It doesn’t get much simpler than this…

Notification ofDocument Availability


Notification of Document Availability Notification of Document Availability Value PropositionValue Proposition

• Allow automation of key use cases within document sharing environments.– Referral Processing– Records Retrieval– Patient Access to Medical Records

• Uses existing, broadly deployed, system infrastructures to support it.


Notification of Document Availability Notification of Document Availability Key Technical PropertiesKey Technical Properties

• Supplies Trigger for Automation• Simple Intermediation of Notification by

forwarding• Uses existing e-mail infrastructure• Commonly available e-mail clients supported• No Protected Health Information Transmitted


Notification of Document AvailabilityNotification of Document Availability Transaction DiagramTransaction Diagram

NotificationSender

NotificationReceiver

SMTP Aether

Send Notification[ITI-25]

Receive Notification[ITI-26]

Receive Acknowledgement[ITI-28]

Send Acknowledgement[ITI-27]


Notification of Document AvailabilityNotification of Document AvailabilityActorsActors

Notification Sender Sends notifications of availability for documents in an XDS registry, and receives acknowledgements of these notifications.

Notification Receiver Receives notifications of availability for documents in an XDS registry, and may optionally send acknowledgments of them.


Profile NameProfile NameStandards UsedStandards Used

RFC-822 Standard for the format of ARPA Internet text messages

RFC-1521 Multipurpose Internet Mail Extensions

RFC-1738 Uniform Resource Locators (URL)

RFC-1939 Post Office Protocol - Version 3

RFC-2368 The mailto URL scheme

RFC-2633 S/MIME Version 3 Message Specification

RFC-2821 Simple Mail Transfer Protocol

RFC-3001 A URN Namespace of Object Identifiers

RFC 3501 Internet Message Access Prototcol – Version 4


Notification of Document AvailabilityNotification of Document AvailabilityTransactionsTransactions

Send Notification Sending a document availability notice.Receive Notification Retrieve a document availability notice.Send Acknowledgement Send an acknowledgement of a

document availability notice.Receive Acknowledgement Retrieve an acknowledgement of a

document availability notice.


Notification of Document AvailabilityNotification of Document AvailabilityBasic Use CaseBasic Use Case

1. Provider A publishes records2. E-mail sent to Provider B3. Provider B can access Records

Provider A

1. Update & Publish Records

2. * Send Notification

Provider B

3. Access Records


Notification of Document AvailabilityNotification of Document AvailabilityIntermediated Use CaseIntermediated Use Case

1. Provider A publishes records2. E-mail sent to Intermediary3. Notification Forwarded to Provider B4. Provider B can access Records

Provider A Provider B

3. * Forward Notification

1. Publish Records

2. * Send Notification

Intermediary

4. Access Records


Notification of Document AvailabilityNotification of Document AvailabilityNotification AttachmentNotification Attachment

<XDSNotificationxmlns='http://www.ihe.net/2005/NAV'

id='urn:uuid:92d03292-84a0-4b86-8139-dd244173ddbb' registry='http://www.ihe.net:8080/XDS'acknowledgement='[email protected]'

><XDSDocumentEntry id='urn:uuid:92d03292-84a0-4b86-8139-dd244173ddbc'

/><XDSDocumentEntry id='urn:uuid:92d03292-84a0-4b86-8139-dd244173ddbd'

/></XDSNotification>


QuestionsQuestions


More information….More information….

• IHE Web sites: www.ihe.net• Technical Frameworks, Supplements

– Fill in relevant supplements and frameworks

• Non-Technical Brochures :• Calls for Participation

• IHE Fact Sheet and FAQ

• IHE Integration Profiles: Guidelines for Buyers

• IHE Connect-a-thon Results

• Vendor Products Integration Statements