Drug Safety Content: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Landenbain (talk | contribs)
New page: <h2>1. Proposed Workitem: <i>Drug Safety Content Definition </i></h2> * Proposal Editor: <Name of author/editor/contact for the proposal> * Editor: <Name of candidate Lead Editor...
 
JohnMoehrke (talk | contribs)
 
(76 intermediate revisions by 4 users not shown)
Line 1: Line 1:
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).


<h2>1. Proposed Workitem: <i>Drug Safety Content Definition </i></h2>
==Summary==
<p>
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.
</p>


    * Proposal Editor: <Name of author/editor/contact for the proposal>
__TOC__
    * Editor: <Name of candidate Lead Editor for the Profile, if known>
    * Date: N/A (Wiki keeps history)
    * Version: N/A (Wiki keeps history)
    * Domain: <Domain name (e.g. Radiology)>


[edit] 2. The Problem


<Summarize the integration problem. What doesn’t work, or what needs to work.>
==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>


==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>


[edit] 3. Key Use Case
==Systems Affected==
<ul>
<li> Electronic Health Record
<li> Safety Reporting System
</ul>


<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>
==Specification==


<Feel free to add a second use case scenario demonstrating how it “should” work. Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>
'''Profile Status:''' [[Comments| Trial Implementation]] 


'''Documents:'''


[edit] 4. Standards & Systems
'' http://ihe.net/Technical_Framework/upload/IHE_QRPH_Suppl_DSC.pdf ''


<List existing systems that are/could be involved in the problem/solution.>


<If known, list standards which might be relevant to the solution>
'''Underlying Standards:'''


:* HL7 Continuity of Care Document
:* ICH E2B standard


[edit] 5. Discussion
[[Category:Profiles]]
 
[[Category:QRPH Profile]]
<Include additional discussion or consider a few details which might be useful for the detailed proposal>
[[Category:CDA]]
 
[[Category:RFD]]
    <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
    * My talk
    * My preferences
    * My watchlist
    * My contributions
    * Log out
 
Navigation
 
    * Main Page
    * Technical Frameworks
    * Domains
    * Committees
    * Process
    * Implementation
    * International
    * Recent changes
    * Help
 
Search
Toolbox
 
    * What links here
    * Related changes
    * Upload file
    * Special pages
    * Printable version
    * Permanent link
 
Powered by MediaWiki
 
    * This page was last modified 23:27, 5 October 2007.
    * This page has been accessed 214 times.
    * Privacy policy
    * About IHE Wiki
    * Disclaimers

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