12 About Oracle Integration Cloud
Description
Oracle Integration Cloud is a secure integration platform as a service (iPaaS) that integrates and automates applications, data, and processes across on-premises and cloud environments, to drive agility and innovation.
- Seamlessly unites enterprise applications with automated, near real-time and batch data integration
- Empowers informed decisions with timely, comprehensive data access
- Limits implementation costs with prebuilt, automated integration tools
- Supports enterprise growth with elastic scalability and high availability
Intended Use and Claims
Oracle Integration Cloud is intended to facilitate the secure exchange, transformation, and routing of healthcare information between disparate healthcare IT systems. The software provides connectivity and interoperability support for healthcare messaging standards, such as HL7, HIPAA X12, and other industry protocols to enable workflow integration and data exchange in support of clinical and administrative operations – both on-premises and in the cloud. Oracle Integration Cloud is not intended to provide clinical decision support, replace professional medical judgment, or provide treatment or diagnostic recommendations.
Indications for Use
Oracle Integration Cloud is recommended for the following uses:
- Integrating EMR and patient record systems.
- Exchanging data between clinical and enterprise business applications.
- Enabling secure provider data sharing.
- Processing insurance claims and billing.
- Supporting telehealth and remote patient monitoring.
- Connecting mobile apps and patient portals.
- Facilitating clinical research initiatives.
Intended User Profile
Oracle Integration Cloud is intended for use by authorized IT and integration professionals in healthcare organizations.
The intended user of the device as defined in Regulation (EU) 2017/745 (April 5, 2017), Article 2, paragraph 37: "‘user’ means any healthcare professional or lay person who uses a device; Article 2, paragraph 38: "‘lay person’ means an individual who does not have formal education in a relevant field of healthcare or medical discipline.”
Information for Safety
Instructions or guidance on how to avoid or minimize risk during the use of a product are included throughout the product Help and Reference Pages
Cautions, Warnings, and Contraindications
Cautions
Consider the cautions below when using the medical device.
Caution:
Not enabling private endpoint support on the secondary instance causes your instance to be inconsistent, resulting in downtime.
Caution:
Ensure that you enable ACL support on the secondary instance prior to performing a failover.
Caution:
If you deselect Restrict network access after configuring allowlist rules, all configured allowlist rules are deleted.
Caution:
If you are using your processes in any way, including calling them from integrations, do not disable Process Automation. Disabling Process Automation permanently deletes your Process Automation instance and all its runtime data. This action can't be undone.
Caution:
Disabling Process Automation permanently deletes your Process Automation instance, including all your processes. If you later re-enable Process Automation, a new Process Automation instance is created with no data from the previous instance.
Caution:
If you are using your visual applications in any way, including calling them from integrations, do not disable Visual Builder. Disabling Visual Builder permanently deletes your Visual Builder instance and all its runtime data. This action can't be undone.
Caution:
Disabling Visual Builder permanently deletes your Visual Builder instance, including all your visual applications. If you later re-enable Visual Builder, a new Visual Builder instance is created with no data from the previous instance.
Caution:
Deleting an Oracle Integration instance can't be undone. This action permanently removes all design-time and runtime data.
Caution:
If you later decrease your data retention period, any data older than the newly selected period would be deleted when you save your selection.
Caution:
You must update your allowlists before upgrade or you'll lose connectivity until it's done.
Caution:
If you don't complete this step, the upgrade will fail.
Caution:
If you update allowlists before the upgrade, don't remove the IP addresses for Oracle Integration Generation 2 yet. You might experience errors. After the upgrade finishes, the Oracle Integration Generation 2 IP addresses are no longer assigned to you and you can remove them.
Caution:
Selecting this option will result in the loss of running (in-progress) and completed process instances. Be careful when selecting this option, especially in a production instance.
Caution:
If your organization has configured a disaster recovery solution, you must use the provided port and hostname, rather than the IP address and hostname. If you use the IP address, the failover for File Server occurs. However, none of your connections to File Server work after the failover.
Caution:
If you connect to File Server and then change
your algorithms, you must update the known_hosts file. If you don't,
your connection to File Server closes and a warning appears.
See Update the List of Supported Algorithms.
Warnings
No warnings exist for Oracle Integration Cloud.
Contraindications
No contraindications exist for Oracle Integration Cloud.
Hardware Requirements
Oracle manages the infrastructure, including hardware, for Oracle Integration Cloud. Organizations that use the connectivity agent and robot agent are responsible for meeting the system requirements for these features.
- Requirements for the connectivity agent: Meet the Requirements for the Connectivity Agent
- Requirements for the robot agent: System Requirements
Instructions for Use
See the Oracle Integration Cloud documentation for instructions about how to use this product.
| Product | Help Pages |
|---|---|
| Oracle Integration Cloud | Oracle Integration 3 on the Oracle Help Center |
Installation, Configuration, and Setup Requirements
For guidance on Oracle and customer responsibilities for patching and upgrade, disaster recovery, data retention, maintenance notifications, and more, see Oracle and Customer Responsibilities.
Cybersecurity Requirements
See Oracle Health and AI (OHAI) Security Program for information about this requirement.
User Qualifications and Required Training
Oracle Integration Cloud users should meet certain qualifications and undergo appropriate training to ensure patient safety, data accuracy, efficiency, and compliance with healthcare regulations.
Additional Resources
The following qualifications are required to use Oracle Integration Cloud:
- Users should possess basic computer literacy, including familiarity with operating systems, navigation, and data entry.
- Users should also understand privacy, security, and regulatory compliance (for example, HIPAA).
- Nonclinical users (such as administrative staff) should have relevant experience in healthcare integration and data exchange.
- Personnel who configure the system, or parts of the system, should have appropriate Information Technology (IT) competence, including experience with software configuration. They should be familiar with the institution’s network, security, and data management policies, and be able to coordinate with clinical staff to ensure that the system is deployed according to its intended use. No clinical training is required for such personnel.
Training Requirements
Optional training is available for users of Oracle Integration Cloud. See Training.
Incidents Reporting
If you experience an issue that adversely impacts patient care or a suspected cybersecurity incident, contact the Oracle Immediate Response Center using the regional phone numbers provided on the Oracle Health Support page.
License Information
See Licensing Information User Manual for Oracle Integration 3 to view a list of copyright and license information for all of the free and open source software.
Patent Information
See the Patents page on Oracle.com for Oracle Integration Cloud patent information.
Warranty
Warranties may vary based on the product purchased, services purchased, or both. See your licensed software agreement for details, or contact your Oracle representative.