Drug Safety Content

1. Proposed Profile: Drug Safety Content

• Proposal Editor: Landen Bain, CDISC Liaison to Healthcare
• Editor: Michael Ibara, Head of Pharmacovigilance Information Management, Pfizer
• Date: January 2008
• Version: 1.0
• Domain: Patient Care Coordination

2. The Problem

While RFD has simplifies data capture for investigator sites, content profiles will extend its value.

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

[edit] 3. Key Use Case

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

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

[edit] 4. Standards & Systems

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

<If known, list standards which might be relevant to the solution>

[edit] 5. Discussion

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