Cisco Digital Network Architecture (Cisco DNA) is an open, extensible and software driven architecture allowing transformation of your business with services to help innovate faster, simplify operations, and reduce risk DNAC three node cluster architecture provides resiliency against failure of hardware components, service infrastructure and application services. The cluster however is not resilient to environmental failures that can bring the cluster down, for example, when the cluster loses power all assurance and automation function will stop. Disaster Recovery provides safeguard against such environmental failures that can bring the cluster down leading to outage otherwise.

The Purchase Order Management is an automated purchase order creation system that creates purchase orders in advance and will flow between the multiple systems. Trend and forecast demand gets approved from the Business Intelligence teams Application. Based on this forecast, it creates the new Purchase Orders and auto selects the locations where the deliveries are to be scheduled. Hence this provides the edge over competing business by making sure that there is never a dearth of goods in the warehouses.

The EHR applications are using to register the patients and adding the PAMI data (Electronic health records) and generating the reports. We have three applications as follows below. Professional (PRO) EHR Touchworks (TW) EHR Sunrise Clinical Manager (SCM) EHR. The patient PAMI data use to exchange across three EHRs via CCD/CIA and incorporate the same data using Import option. If data will exchange via CIA across three EHRs than its called as Fused view data. Here mainly focusing on Integration testing across three EHRs. The DBMotion (Community) is the data repository of three EHRs, whatever data will add in any one of the EHR than the same data will be store in DB Motion (Community) as well as respective database.

A data exchange platform to facilitate transfer of data between iSupplyCore, iRelease, sIRT and other Clinical Supply chain related systems in the form of XML. Specific interfaces between SAP, D2P, iRelease and Cenduit sIRT. Currently there is no single system/platform which can be used by TRD for drug accountability from patient level down to drug product/substance and corresponding raw material/Excipient in case of a recall need or HA audit. The Objective of the D2P Interface system is to provide for such a platform which can be used not only for Drug accountability but also for other reporting capabilities (ex: operational cross-study DSM/RegioDis reports). This single system/platform would cover data from studies supported by Standard IRT and studies which do not use standard IRT (non-IRT). The business process is performed in the business systems providing and consuming the data between SAP, D2P, iRelease and Cenduit sIRT. User interaction with the system: Pass through – Refers to a mode where data from the source/receiving systems is passed directly to the consuming system. Canonical definitions are applied while receiving and transferring the data. The D2P Data store doesnt retain these data. Store and Send – Is where the data from the source is first stored in D2P Data store before sending the data to the consuming system. Canonical definitions are applied while receiving and transferring the data. The below mentioned messages are exchanging between SAP, D2P, iRelease and Cenduit sIRT. CentralStockFile, Batch Genealogy, CountryOfCompliance, StockTransferOrderDelivery, STO Delivery Acknowledgement, Planned STO Delivery Date, STO Delivery Cancellation, Planned STO Delivery Cancellation, Planned STO Delivery InCountryRelease, STOGoodsIssue, ConfirmationOfGoodsReceiptAtDepot, Kit Expiry Extended STO Delivery, Extended Kits Released InCountryRelease, PCNBatchBlock.

This is a scheduled one way task. It transfers the data from CIRT to COMET (sftp server). The purpose of 1-way transfer from CIRT to COMET (sftp server) is to transfer the stock levels of packed medication on a daily basis. There should be three activities which are as follows: 1. Audit the material data changes in study level. 2. Generate the stock details in study level & push into the COMET staging database when running the Study level task. 3. Generate the XML file for all the study stock details available in the COMET staging database & upload the same to COMET sftp server path when running the Global VB task.

The Material Block Module will be developed as an integrated application within CIRT core platform. This functionality allows user to Block, Unblock or update materials status to Damaged after having been block. This module will allow blocking materials, preventing them from being shipped to depots and sites and from being dispensed to patients. The module will also allow: unblocking blocked materials & setting to Damaged blocked materials. Any block or unblock or damage cycle requires user 1 to initiate the request and user 2 to approve it - the two users cannot be the same.

Cenduit created custom programming for transaction submissions, which when selected, will call the Medidata web service API via HTTP(s) and pass the require data fields in real time communication. The integration will be a one-way data transfer from CIRT to RAVE. It will outline the file format needed to successfully pass data to the Medidata RAVE database, and provide a mapping of data fields that need to be sent. Medidata RAVE API follows the CDISC Operational Data Model (ODM) v1.3 standards. On submission of the following Rich forms (screening, randomization, medication dispensing visits), data will be transmitted, via the RAVE web service, to the RAVE database. This transmission should be done in real-time, and the submit button for the forms must be modified. This transmission cannot be handled by a task triggered from the form submission; it must be designed into the submission so that data is passed real-time.

Drug Reconciliation Module will allow users to confirm Drug Destruction. Blinded and Unblended Drug Return Reports. Central Drug Release This functionality allows user to assign an expiry date, PCN and Drug Product batch data for specific materials sequence ranges per material type. Multi-Country-Caesar (MCC) This is a scheduled task. This task does 2-way data (Initial Supply/Resupply and Expiry Update) transfers between CIRT and MCC . Study Medication Batch Block module identifies functionality related to Block/Unblock one or more PCN and/or batches of study medication into CIRT in order to prevent dispensing to Patients and shipments to sites. This functionality allows a user to temporarily of definitely block medication of a certain PCN or/and Drug Product Batch (Drug product batch data may be made of Description, Batch, basis and Variant) Expiry Date Update module functionality allows user to update the expiry date of one or more kits into CIRT.

Drug Reconciliation Module will allow users to confirm Drug Destruction. Blinded and Unblended Drug Return Reports.

Central Drug Release This functionality allows user to assign an expiry date, PCN and Drug Product batch data for specific materials sequence ranges per material type.

Multi-Country-Caesar (MCC) This is a scheduled task. This task does 2-way data (Initial Supply/Resupply and Expiry Update) transfers between CIRT and MCC .

Medidata RAVE API follows the CDISC Operational Data Model (ODM) v1.3 standards. On submission of the following Rich forms (screening, randomization, medication dispensing visits), data will be transmitted, via the RAVE web service, to the RAVE database

1. A data exchange platform to facilitate transfer of data between iSupplyCore, iRelease, sIRT and other Clinical Supply chain related systems in the form of XML.
2. Specific interfaces between SAP, D2P, iRelease and Cenduit sIRT.

Cisco Digital Network Architecture (Cisco DNA) is an open, extensible and software driven architecture allowing transformation of your business with services to help innovate faster, simplify operations, and reduce risk