Difference between revisions of "Drug Safety Content"

Latest revision as of 13:56, 4 November 2019

Drug Safety Content (DSC) describes the content and format to be used to pre-populate data for safety reporting purposes. DSC is a content profile that uses transactions described within Retrieve Form for Data-capture (RFD).

Summary

DSC is part of a set of profiles that create interoperability between EHRs and specialized research systems, resulting in EHR-enabled research. The purpose of this profile is to support a standard set of data in Continuity of Care Document format which the EHR provides for use in reporting adverse events as it relates to Drug Safety. In addition this profile will reference the ability to convert this output into the ICH E2B(R3) standard.

Benefits

DSC both saves labor and improves the quality of drug safety data. By eliminating duplicate data entry, the use of DSC saves time in the process of completing a drug safety report form. By using existing EHR data to automatically pre-populate the form, DSC eliminates data entry errors, thus improving data quality.

Details

DSC is activated by the Retrieve Form for Data-capture (RFD) profile at the point where RFD retrieves a data safety from a safety reporting system. DSC defines the export document based on HL7's Continuity of Care Document, and provides a mapping to the ICH E2B(R3) standard.

Systems Affected

Electronic Health Record
Safety Reporting System

Specification

Profile Status: Trial Implementation

Documents:

http://ihe.net/Technical_Framework/upload/IHE_QRPH_Suppl_DSC.pdf

Underlying Standards:

HL7 Continuity of Care Document
ICH E2B standard

@@ Line 1: / Line 1: @@
-<h2>1. Proposed Profile: <i>{{PAGENAME}}</i></h2>
+Drug Safety Content (DSC) describes the content and format to be used to pre-populate data for safety reporting purposes.  DSC is a content profile that uses transactions described within Retrieve Form for Data-capture (RFD).
-<ul>
+==Summary==
-    <li> Proposal Editor: <i>[[user: landenbain | Landen Bain, CDISC Liaison to Healthcare ]]</i>
+<p>
-    <li> Editor: <i>Michael Ibara, Head of Pharmacovigilance Information Management, Pfizer</i>
+DSC is part of a set of profiles that create interoperability between EHRs and specialized research systems, resulting in EHR-enabled research. The purpose of this profile is to support a standard set of data in Continuity of Care Document format which the EHR provides for use in reporting adverse events as it relates to Drug Safety. In addition this profile will reference the ability to convert this output into the ICH E2B(R3) standard.
-    <li> Date: <i> January 2008 </i>
+</p>
-    <li> Version: <i> 1.0 </i>
-    <li> Domain: <i> Patient Care Coordination</i>
-</ul>
-<h2> 2. The Problem </h2>
- <p><i><b>While RFD simplifies data capture for investigator sites, content profiles will extend its value.</b></i></p>
-<p>RFD has proved itself to be particularly useful in two use cases that pertain to the biopharmaceutical industry: collection of clinical trial data (addressed in the companion profile “Clinical Research Data Collection Fields”, and drug safety, the topic of this proposal.  The drug safety use case addressed here is the post-market reporting of adverse drug events.  This reporting begins with a trigger event within the EHR which identifies the need to report an adverse event.  RFD summons a drug safety data capture form from the appropriate source, and the form is completed by the EHR user, assisted by auto-population scripts within the EHR.  The problem which this profile addresses is the lack of standard content for the auto-population. </p>
+__TOC__
-<p>The proposed content profile will align the data requirements of the RFD data safety report with HL7’s ICSR (E2B) standard.  ICSR provides the basis for identifying the data elements required from the EHR, and greatly simplifies the involvement of the EHRs in drug safety reporting.
-This content profile will also complement the Query for Existing Data profile currently in development.  An ICSR-based content profile would provide the list of data elements that an EHR should have on hand to respond to an external query from a drug safety sponsor.</P>
-<h2>3. Key Use Case</h2>
-<p> The point of departure for this use case is a patient care site which currently reports drug safety information using RFD without a content profile.  The ‘before’ state shows the use of RFD without a content profile.  The ‘after’ state describes the use of RFD in concert with the proposed content profile. </p>
-<p><b>Before Drug Safety Content:</b> A physician discovers a suspected adverse event during a patient outpatient visit.  The physician uses RFD to fetch a drug safety form from the appropriate source and completes the form by hand. </p>
+==Benefits==
+<p>
+DSC both saves labor and improves the quality of drug safety data. By eliminating duplicate data entry, the use of DSC saves time in the process of completing a drug safety report form. By using existing EHR data to automatically pre-populate the form, DSC eliminates data entry errors, thus improving data quality.
+</p>
-<p><b>After Drug Safety Content:</b>  A physician discovers a suspected adverse event during a patient outpatient visit.  The physician uses RFD to fetch a drug safety form from the appropriate source.  The EHR automatically provides the data elements specified in the Drug Safety Content Profile, and the forms manager populates the form and returns it to the form filler for display.  The physician reviews the partially completed form, and fills in those sections which the content profile did not specify.   RFD returns the data to the Forms Receiver.</p>
+==Details==
+<p>
+DSC is activated by the Retrieve Form for Data-capture (RFD) profile at the point where RFD retrieves a data safety from a safety reporting system. DSC defines the export document based on HL7's Continuity of Care Document, and provides a mapping to the ICH E2B(R3) standard.
+</p>
-<h2>4. Standards & Systems </h2>
+==Systems Affected==
-<h4> Systems</h4>
 <ul>
-<li>Participating EHRs;
+<li> Electronic Health Record
-<li>Participating drug safety systems.
+<li> Safety Reporting System
 </ul>
-<h4> Standards </h4>
+==Specification==
-<ul>
- <li>CDISC standards: ODM, SDTM, CDASH, Terminology.
-<li>W3C standards: XForm, OWL, RDF.
-<li>HL7 standards: ICSR.
-</ul>
-<h2>5. Discussion </h2>
-<Include additional discussion or consider a few details which might be useful for the detailed proposal>
-    <Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>
-    <What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>
-    <What are some of the risks or open issues to be addressed?>
-<This is the brief proposal. Try to keep it to 1 or at most 2 pages>
-<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>
-Retrieved from "http://wiki.ihe.net/index.php?title=Brief_Proposal_Template"
-Category: Templates
-Views
-    * Article
-    * Discussion
-    * Edit
-    * History
-    * Move
-    * Watch
-Personal tools
-    * Landenbain
+'''Profile Status:''' [[Comments| Trial Implementation]]
-    * My talk
-    * My preferences
-    * My watchlist
-    * My contributions
-    * Log out
-Navigation
+'''Documents:'''
-    * Main Page
+'' http://ihe.net/Technical_Framework/upload/IHE_QRPH_Suppl_DSC.pdf ''
-    * Technical Frameworks
-    * Domains
-    * Committees
-    * Process
-    * Implementation
-    * International
-    * Recent changes
-    * Help
-Search
-Toolbox
-    * What links here
+'''Underlying Standards:'''
-    * Related changes
-    * Upload file
-    * Special pages
-    * Printable version
-    * Permanent link
-Powered by MediaWiki
+:* HL7 Continuity of Care Document
+:* ICH E2B standard
-    * This page was last modified 23:27, 5 October 2007.
+[[Category:Profiles]]
-    * This page has been accessed 214 times.
+[[Category:QRPH Profile]]
-    * Privacy policy
+[[Category:CDA]]
-    * About IHE Wiki
+[[Category:RFD]]
-    * Disclaimers