Industry solutions for healthcare use multiple components in Informatica Intelligent Cloud Services.
Industry solutions use the following components:
•Data services repository
•Data services API
•Industry data service customizer
•Mapping templates
•Connections
•Data Services transformation
•Hierarchical mappers
•Intelligent structure models
•Mapping tasks
Data services repository
The data services repository is a central repository of pre-built data services that process, validate, and transform industry-standard messages. You can also upload your own services to the repository.
The name of a data service indicates the industry standard, the version of the standard, the message type, and the service usage type, in the following syntax:
A parser data service receives and parses messages from your partners while a serializer data service serializes and sends messages to your partners. You can also use a restricted serializer data service that uses stricter rules to validate HIPAA messages before sending them to your partners.
You can view, create, edit, and delete data services on the Data Services Repository page in Administrator.
The data services API runs data services using Informatica Intelligent Cloud Services REST API. You pass a file to the API, and a data service processes it.
For more information, see Data services in the REST API Reference.
Industry data service customizer
You can use the industry data service customizer to customize an industry-standard message and publish it as a custom data service to the data services repository.
A customizer provides out-of-the-box message types based on the messaging standard. You select a message type and customize the message structure by adding, editing, and removing elements.
A mapping template is a pre-made mapping that contains pre-populated transformations. You can click each transformation in the mapping to see the purpose of the transformation, how the transformation is configured, and which parameters are used.
A set of mapping templates for common use cases is available under the Industry Solutions category. The templates are pre-configured and include the common logic needed to handle a specific use case using data services. Each template includes a Data Services transformation that uses a data service from the data services repository to parse incoming messages and output the data in XML format.
Connections are used to access data in cloud and on-premises applications, platforms, databases, and flat files. They specify the location of sources, lookup objects, and targets. For industry solutions, Data Integration offers several industry-specific connections such as FHIR REST-based connections and MLLP connections.
You use connectors to create connections. You can create a connection for any connector that is installed in your organization.
To create a connection, use the Connections page in Administrator. The Connections page lists all connections that have been configured in the organization.
For more information, see Connections in the Administrator help.
Data Services transformation
You can use the Data Services transformation to run a data service from the data service repository within a mapping in Data Integration. The data service parses or serializes industry-standard messages in the mapping flow. For example, you can use a data service to parse and serialize HL7 messages that you exchange with your healthcare partners.
When you define the data service in the transformation, you can use one of the following options:
•Use a specific data service name to process a single message type for a specific standard and usage type.
•Use a dynamic service name to process messages for multiple message types from different standards and usage types.
The Data Services transformation passes the processed message data to the downstream transformation in a file or as a buffer. It can create additional output fields based on the status tracing level and the data service usage type and send different output types to different targets. For example, you can send message data to one target and send status tracing reports to another target.
A hierarchical mapper maps a hierarchical schema, such as the schema for an industry-standard message, to another hierarchical schema. For example, you can map the XML output of a parser data service to a target XSD file.
You can use a hierarchical mapper in a Data Services transformation to process hierarchical input and convert it to hierarchical output that uses a different hierarchical structure.
A CLAIRE® intelligent structure model is an asset that determines the underlying patterns and structures of the input that you provide, and it can be used to parse long, complex files with little or no structure.
Intelligent structure models can provide pre-built mappers that convert XML data to relational format. For example, you can find pre-built mappers that convert HL7 and FHIR data to relational structures.