Notification of Document Availability

From IHE Wiki

(Redirected from NAV)
Jump to: navigation, search

Contents


Summary

Notification of Document Availability (NAV) defines a mechanism for point-to-point notifications between systems or users within an XDS Affinity Domain or between different XDS Affinity Domains.

Benefits

NAV provides a mechanism for point-to-point notifications.

Details

NAV defines a mechanism for point-to-point notifications between systems or users within an XDS Affinity Domain or between different XDS Affinity Domains. These notifications can be used to trigger various activities within applications that implement both XDS and NAV. The Notification of Document Availability Profile specifies the use of SMTP and related standards for sending notifications, and the XML Digital Signature Core for creating a manifest of documents which are the subject of the notification.

This profile may be used to support:

  • Responses to requests for records between providers.
  • Referrals between providers.
  • Guiding Patients in accessing specific parts of their health records.

The Notification of Document Availability Profile (NAV) defines the format, content, encoding and transmission of notification messages and acknowledgements between NAV Actors and a known recipient (either a person or system) that participate in the same XDS Affinity Domain or between different XDS Affinity Domains. These notifications are used to indicate that meta-data for one or more new or existing documents are available in the XDS Registry.

The manner in which a Notification Receiver is associated with and XDS Document Consumer is not defined in this profile to allow a broad range of implementation approaches.

Systems Affected

Systems involved in this profile are:

  • EHR, EMR, HIE, HIO

Actors & Transactions: NAV-Actor-Transaction.jpg

Specification

Profile Status: Trial Implementation

Documents:

  • Vol. 1 - Section 12
  • Vol. 2a - Sections 3.25, 3.26, 3.27, 3.28


Underlying Standards:

  • xmlsig-core XML-Signature Syntax and Processing, 2002, W3C, Donald Eastlake, Joseph Reagle, David Solo, et. al.
  • RFC-822 Standard for the format of ARPA Internet text messages, 1982, IETF, David H. Crocker
  • RFC-1521 Multipurpose Internet Mail Extensions, 1993, IETF, N. Borenstein, N. Freed
  • RFC-1738 Uniform Resource Locators (URL), 1994, IETF, T. Berners Lee, L. Masinter and M. McCahill.
  • RFC-2368 The mailto URL scheme, 1998, IETF, P. Hoffman, L. Masinter and J. Zawinski
  • RFC-2821 Simple Mail Transfer Protocol, 2001, IETF, J. Klensin
  • RFC-3001 A URN Namespace of Object Identifiers, 2000, IETF, M. Mealing
  • RFC 1939 Post Office Protocol - Version 3, 1996, IETF, J. Meyers, M. Rose
  • RFC 3501 Internet Message Access Protocol – Version 4, 2003, IETF, M. Crispin


See Also

Related Profiles

This page is based on the Profile Template

Personal tools