By itself, a CTMS serves a critical purpose in clinical research management. Building on that foundation, sites often integrate their CTMS with other enterprise systems, resulting in improvements to staff efficiency, data quality, and even patient safety.
Here are a few of the most common CTMS integrations:
Protocol and Subject Information: Typically leveraging the IHE HL7 Retrieve Process for Execution (RPE) protocol, this integration sends protocol number, title and principal investigator to an EMR system. Also, subject data can be sent from the CTMS to the EMR so a patient can be flagged within the EMR as an enrolled research participant.
Demographics: A patient demographics interface is used to transfer demographic data such as contact information, patient identifiers, and date of birth from the site’s EMR system to a CTMS. This saves the research organization staff time and reduces room for error when manually entering data.
Protocol Billing Grid: This interface allows study team members to indicate procedure billing designations at the protocol level within the CTMS, which then provides this information to an EMR for use in determining how to route charges. The ultimate goal of this interface is to support billing compliance while centralizing and streamlining communication among study and financial teams.
General Ledger: This receivables interface allows a site to manage the payment of the CTMS-initiated invoice in the general ledger system, and then reconcile the payment for those research activities in the CTMS. Connecting these systems ensures that research and financial teams have access to consistent, up-to-date information on study-related invoice receivables.
Other Research Systems: A CTMS can be linked with other systems throughout a site, including eRegulatory, eIRB, EDC, participant payments, and more. Where a CTMS may lack a native integration with these systems, they can sometimes be connected via an Application Programming Interface (API).