COMPOSABLe AUTOMATION™
Purpose Built Components™
Purpose Built Components™ (PBCs) are the foundation for composable automation.
Configurable components that are reusable across use cases
A Purpose-Built Component is a coding approach that abstracts the complexity of writing low-level code while incorporating configuration to support reuse across use cases. In the workflow design, PBCs are connected and configured to describe the intended workflow for the business.
Why are PBCs important?
Workflow designs are traditionally difficult to understand and codify. Using PBCs, business workflows can be accelerated in their design, testing, and migration to production, thereby reducing the time to deliver customer solutions. Complex data and API orchestration requirements are decomposed into PBCs to configure into customer-specific workflows.
Types of PBCs
Product PBCs
A robust inventory of product PBCs developed and supported by HealthLX. Business analysts define requirements and develop PBCs during implementation. Completed PBCs are then maintained within future product releases.
Implementation PBCs
Rapid prototyping of workflow capabilities as necessitated by the customer’s needs, often occurring at the point of implementation by software engineers. Implementation PBCs are often associated with legacy systems in the customer environment.
Customer Developed PBCs
HealthLX supports customer-developed PBCs leveraging the platform toolset and methods. Training is available to teach teams how to develop PBCs. Our customers can build their own PBCs for unique integrations. All customer-developed PBCs require certification by our product team to ensure ongoing support in future product releases.
The value of PBCs driving Composable Automation:
Enhanced Flexibility and Scalability
Modular Components: Composable architecture’s emphasis on smaller, function-specific components makes it easier to adapt and scale automation efforts. Each PBC component can be developed, deployed, and updated independently, allowing for more agile responses to changing requirements.
Reusability: PBCs’ modular and configurable nature in a composable architecture facilitates reuse across different automated workflows, reducing development time and effort.
Dynamic Configuration and Adaptation
Rapid Configuration: Composable architecture allows for the dynamic configuration of PBCs to meet specific automation needs. This enables businesses to adapt their automation strategies quickly to evolving market trends or operational challenges.
Adaptive Workflows: Automation workflows can be easily modified, extended, or optimized by swapping, adding, or removing PBCs without disrupting the overall system. This adaptability is essential for maintaining efficient operations over time.
Improved Integration Capabilities
Standardized Interfaces: Composable PBCs often expose standardized interfaces, simplifying the integration of diverse systems and applications. This is crucial in enterprise application integration (EAI), where different systems might need to communicate and work together seamlessly.
Interoperability: Composable architecture enhances interoperability among disparate systems by adhering to common standards and protocols, a key aspect of effective automation in complex enterprise environments.
Cost and Time Efficiency
Lower Development Costs: By leveraging reusable PBCs, organizations can reduce the time and resources required to develop and implement automation solutions.
Faster Time-to-Market: Composable architecture enables quicker assembly of automation solutions, accelerating time-to-market for new services or capabilities.
Easier Maintenance and Upgrades
Simplified Maintenance: Because each PBC is independent, maintenance and updates can be carried out with minimal impact on the overall system. This reduces downtime and improves system reliability.
Continuous Improvement: The ease of updating and replacing individual PBCs facilitates continuous improvement of automation processes, ensuring they remain effective and efficient over time.