![]() The integration will always send Reported from Study as the report type. If this value is not entered and the product name is not entered on a form in Oracle Health Sciences InForm, the integration sends the string StudyDrug when any drug information is entered in Oracle Health Sciences InForm and StudyDevice when any device information is entered. If the product name is not mapped in the Logical Schema, the value in StudySponsorDrug field in the trial database will be sent as the Product Name for the Drug and/or Device product. The Initial Received Date is the date in the time zone of the site when the adverse event was marked as serious or reportable. If qualification code for the reporter is not mapped to an item in the Safety Logical Schema or the value is not entered, the qualification code of the reporter will be sent as Physician. The name and address of the site where the subject experienced the adverse event is considered as the address.īased on the above details, the Safety user searches for the Principal Investigator of that site where the serious adverse event had occurred and enters the details of the Principal Investigator as the primary reporter of the case in Oracle Argus Safety. ![]() The Site mnemonic concatenated with the site name will display as the institution of the reporter in Argus. This user is considered the primary reporter of the case while sending the event details to Oracle Argus Safety. ![]() The full name of the user who marked the AE as serious or reportable. The following details are sent to Safety regarding the serious adverse event: There is some data that is pre-populated by the integration when sending the safety data. This last step is optional and can be disabled. Once the case is accepted or rejected either manually or automatically in Argus, the case ID, status, and rejection reason (if applicable) will be sent back to Oracle Health Sciences InForm. If not, the XML file will appear in the Pending E2B Reports screen in Argus. If auto-acceptance is configured in Argus, a case will be created. The AIA layer will transform the message to an E2B+ XML file. For more details, see InForm Publisher On Demand 1.0.2.0 Installation Guide. This message will include adverse events, concomitant medications, and labs that fall into the time frames specified in Oracle Health Sciences InForm Publisher. Oracle Health Sciences InForm Publisher will monitor the InForm Trial database and send a message containing all the data items mapped in the Safety Logical Schema to the AIA layer. ![]() The Study Designer in Central Designer will define the items to be sent and the trigger to send the data. However, the following will always happen. The steps will differ based on the trial design. The example data architecture resources below enable you to visualize how the interoperable integration of sensor data across a unified platform can fulfill its promise to improve patient lives.This integration automates the sending of serious adverse event data from the EDC system, Oracle Health Sciences InForm, to the safety system, Oracle Argus Safety. The working group conducted three workshops, which entailed deep dives into use cases for care delivery, clinical development, and the integration between these areas. As part of the Sensor Data Integrations project, Oracle collaborated with 11 industry partners and the Digital Medicine Society (DiMe) to curate resources that enable researchers, data scientists, decision-makers, and clinicians to use increasingly ubiquitous sensor data to make better and more reliable decisions faster. The seamless integration of sensor data is critical to improving the efficiency and effectiveness of clinical decision-making at scale in both research and healthcare. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |