This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Product UVRR"

From HL7Wiki
Jump to navigation Jump to search
Line 22: Line 22:
 
*ANSI/HL7 V3 RRCS, R1-2005, R2-2006 - HL7 Version 3 Standard: Public Health Reporting: Individual Case Safety Report, Release 1; 4/25/2005, Release 2; October 2006  
 
*ANSI/HL7 V3 RRCS, R1-2005, R2-2006 - HL7 Version 3 Standard: Public Health Reporting: Individual Case Safety Report, Release 1; 4/25/2005, Release 2; October 2006  
 
*HL7 V3 GIN, R1 - HL7 Version 3 Standard: Generic Incident Notification, Release 1; March 2007  
 
*HL7 V3 GIN, R1 - HL7 Version 3 Standard: Generic Incident Notification, Release 1; March 2007  
*V3: Public Health: Tuberculosis Domain Analysis Model, Release 1
+
*V3: Public Health: [[Product_TB_DAM|Tuberculosis Domain Analysis Model]], Release 1
 
*HL7 Implementation Guide for CDA Release 2: Public Health Case Reporting, Release 1 (US Realm)
 
*HL7 Implementation Guide for CDA Release 2: Public Health Case Reporting, Release 1 (US Realm)
  

Revision as of 22:07, 11 November 2009

Product Brief - Public Health Reporting Domain

back to Main_Page
back to Product_List

Product Name

HL7 V3: Public Health Reporting

Topics

  • Individual Case Safety Report
  • Generic Incident Notification
  • Safety Reporting Management
  • Case Investigation Topic, aka Notifiable Condition Report, withdrawn

Standard Category

  • Health Information Exchange Standards

Integration Paradigm

  • Messaging

Type

Normative, ANSI standard (ICSR R1) DSTU (ICSR R2)

Releases

  • ANSI/HL7 V3 RRNCR, R1-2004 - HL7 Version 3 Standard: Public Health Reporting: Case Investigation Topic, Release 1; 11/3/2004 aka Notifiable Condition Report, withdrawn
  • ANSI/HL7 V3 RRCS, R1-2005, R2-2006 - HL7 Version 3 Standard: Public Health Reporting: Individual Case Safety Report, Release 1; 4/25/2005, Release 2; October 2006
  • HL7 V3 GIN, R1 - HL7 Version 3 Standard: Generic Incident Notification, Release 1; March 2007
  • V3: Public Health: Tuberculosis Domain Analysis Model, Release 1
  • HL7 Implementation Guide for CDA Release 2: Public Health Case Reporting, Release 1 (US Realm)

Summary

The domain includes messages and documents that are specifically designed to support reporting and investigation in the public health context. This scope includes:

Communications within a health provider organization,
Messages sent to public health regulatory agencies or other patient safety/quality improvement organizations from outside parties,
Reporting among health care providers, manufacturers, and public health or patient safety/quality improvement organizations.


Description

The Public Health Reporting Domain Information Model captures the information to be exchanged about conditions or events that are to be subject to public health review or investigation. The model initially focused on the needs of the US Federal Government for HL7 messaging in the areas of disease surveillance and the reporting of adverse events, reactions or problems related to regulated products, as well as reporting by parties investigating incidents of public concern. However, the model is not limited to US based reporting, or to regulatory application - but has been generalized to be applicable across the HL7 community.

  • The Public Health Reporting Domain contains specifications from a variety of healthcare focus areas (e.g., patient safety, consumer safety, environmental safety; regulatory vs. non-regulatory safety monitoring). Analysis is underway using an HL7 DAM (Domain Analysis Model) to determine whether a common Domain Information Model can support this variety of focus, or whether additional domain models (and thus additional domains) are needed. If new domains are established, the specifications in the present Public Health Reporting domain are likely to be distributed among those new domains.
  • It should be noted that there is not currently a generally accepted Domain model for the PORR domain. Work is currently in progress involving PHER, Patient Safety, RCIRM, etc. to develop such a model.

Business Case (Intended Use, Customers)

Benefits

Implementations/ Case Studies (Actual Users)

Resources

Work Groups

Education

Certification Available
  • none

Presentations

Relationship to/ Dependencies on, other standards

Links to current projects in development