Services

In the following chapter, we will explore two types of connections between services:

1. External Service: This refers to a service that is deployed within an external environment, typically outside the direct control or infrastructure of the primary organization. Interactions with such services often require specific integration strategies to manage external pressures and ensure data quality.
2. Internal Service: In contrast, this type of service is deployed within the same environment as the main application, often leveraging technologies like Kubernetes (K8s) for orchestration. These services may take advantage of automatic discovery mechanisms using K8s, streamlining the process of identifying and connecting with other internal services.

Understanding these distinctions is crucial for designing effective integration solutions tailored to both internal and external service requirements.

External Service

QIP easily integrates with external services by leveraging specifications that define data formats, protocols, or business rules. The only required step is to upload specifications to QIP using standardized templates. Once uploaded, specifications are stored in the System Catalog , a centralized repository for all imported configurations.

System Catalog Functionality:

• Stores Specifications: The Catalog retains all imported specifications, ensuring consistency and accessibility across workflows.
• Parameter Customization: Users can define environment details (e.g., production vs. test), API paths, query parameters, and other metadata directly in snapshots linked to the Catalog.
• Streamlined Chain Configuration: By referencing the Catalog, developers avoid manual parameter setup. For example, specifying a Medicaid ID or NDC list for claims analysis becomes automated.

This design reduces errors and accelerates deployment, as specifications like value sets or security protocols are pre-configured and reusable.

Internal Service

Auto Discovery is a service that automates the collection and storage of system specifications in a unified repository. This eliminates the need for manual tracking, ensuring all API definitions, configuration parameters, and service details are accessible in one location.

Key Features:

• Real-Time Accessibility: Users can search for any service specification at any time to validate compatible APIs or dependencies.
• Automated Updates: The system continuously scans and updates specifications, reducing errors caused by outdated or incomplete data.
• Process Optimization: By centralizing specifications, Auto Discovery simplifies API compatibility checks and accelerates development cycles.

Benefits:

• Cost Efficiency: Reduces redundancy and rework by ensuring teams use accurate, up-to-date specifications.
• Risk Mitigation: Minimizes misconfigurations through automated validation of specifications against defined standards.