Keith W' Boone

1
Notification of Document Availability(NAV)
Keith W. Boone Dictaphone Corporation IHE ITI
Technical Comittee
2

• Providers and Vendors
• Working Together to Deliver
• Interoperable Health Information Systems
• In the Enterprise
• and Across Care Settings

3
Notification of Document Availability Abstract

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

4
Notification of Document Availability Scope
It doesnt get much simpler than this
5
Notification of Document Availability Value
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.

6
Notification of Document Availability Key
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

7
Notification of Document Availability Transaction
Diagram
Send NotificationITI-25
Receive NotificationITI-26
NotificationReceiver
NotificationSender
Send AcknowledgementITI-27
Receive AcknowledgementITI-28
8
Notification of Document AvailabilityActors

• 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.

9
Profile NameStandards 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

10
Notification of Document AvailabilityTransactions

• 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.

11
Notification of Document AvailabilityBasic Use
Case
Provider A
Provider B
1. Update Publish Records
2. Send Notification
3. Access Records

• Provider A publishes records
• E-mail sent to Provider B
• Provider B can access Records

12
Notification of Document AvailabilityIntermediate
d Use Case
Provider A
Provider B
Intermediary
1. Publish Records
2. Send Notification
3. Forward Notification
4. Access Records

• Provider A publishes records
• E-mail sent to Intermediary
• Notification Forwarded to Provider B
• Provider B can access Records

13
Notification of Document AvailabilityNotification
Attachment

• ltXDSNotification xmlns'http//www.ihe.net/2005/N
  AV' id'urnuuid92d03292-84a0-4b86-8139-dd244173d
  dbb' registry'http//www.ihe.net8080/XDS' ackn
  owledgement'emailaddress_at_ihe.net' gt
• ltXDSDocumentEntry id'urnuuid92d03292-84a0-4
  b86-8139-dd244173ddbc' /gt
• ltXDSDocumentEntry id'urnuuid92d03292-84a0-4
  b86-8139-dd244173ddbd' /gt
• lt/XDSNotificationgt

14
Questions
15
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