Adeptia HL7 Integration Solution Technical Features
Key questions that companies often think about when integrating HL7 are related to how well the product can process the HL7 messages out-of-the-box with preconfigured functions that are readily available.
Here we have listed some of the key questions and how Adeptia supports these features as part of its HL7 healthcare integration solution.
Is your HL7 integration solution ready (to a state where customization can be done) to support new HL7 message formats?
Yes, HL7 message formats can be customized in Adeptia. User can use a base or a standard template and can modify the schema and use it for that custom message. User can also take an existing format or a schema and make changes and create a new copy. This allows for faster onboarding time where formats don’t have to be defined from scratch.
User can define any message format as Adeptia provides all the message standards as described above. In addition to formats we also support other formats such as Flat files, CSV, XML, Excel, Fixed Width, JSON etc. All protocols (FTP, SFTP, SOAP, REST, AS2, VAN, HTTPS, MQ, Database/JDBC, LAN, WebDAV, MLLP/TCP etc.) are supported out of the box. Also user can define their own communication methods/plugins or expand on the ones that are already included. Adeptia also support application protocols that are native to CRM, ERP systems such as SAP, Database (JDBC), Insurance applications such as POINT, Applied, AMS, Guidewire, ClaimsPlus, PolicyPlus, and CSC systems.
Does the tool include a library of Healthcare industry standard formats?
Adeptia provides all Healthcare standards such as HIPAA, HL7, NCPDP etc. The data dictionaries are available for download.
What level of compliance or validations does Adeptia provide?
Adeptia supports full validation of Healthcare messages and also recommends different strategies on how to accomplish the compliance for your inbound and outbound messages with in-built or third-party compliance tools.
Does the tool contain an extraction layer (set up in the tool) which allows the source/vendor file to be mapped to it?
Yes, the extraction layer is part of the source configuration where we provide the location in the trigger rules on when to pick up the message. Once a new file is dropped into a location or a new message arrives through the message transport protocols we would automatically parse and extract the data and convert the data based on the orchestration defined by the user. When Adeptia picks up and parses a message it matches the incoming data with its defined schema. If there are parsing errors such as data type mismatch or invalid records due to any number of reasons then those errors are shown in the monitoring dashboard and email is sent out to user to review and take corrective actions. Error descriptions would describe why that record failed. These parsing errors can be routed to a file for further processing, attached to an email or loaded into a database for reporting.
Provide examples of how customers access your website to retrieve ad hoc reports by selecting data elements.
Some of the common reports are the Transaction and B2B Reports that allows customers to login to the Adeptia platform and click on Dashboard to see the custom reports that the team has configured for their usage. Adeptia supports full custom reports and dashboard capability. It has a reporting engine that can pull data with different parameters and provide a PDF, HTML, Excel based reports to the customers and can also deliver these reports as mobile apps or via email.
Customers can also log into the Adeptia Connect platform and click on Dashboard to see if their files were processed. Customer can also see an error report and see the list of errors resulting from the HL7 message exchange.
Does the HL7 integration allow for transformation?
Graphical Data Mapping allows users to map source to any target format. The mapper interface has full list of pre-built functions to do lookups, corss-reference, external calls to databases, APIs, and other programs. Pre-built functions include, Math(add, multiply, divide etc) , String (concat, substring, tirm, translate etc) , Aggregation, Merge, Sort, Conditional (If else then), and more advanced XSL functions. The code generated is a standard XSL and not proprietary. The documentation is also automatically generated.
Does the HL7 integration have a robust exception handling and reporting?
Yes, this is key to Adeptia’s customer data onboarding platform. Each transaction run is monitored and its run-time results generate messages in terms of failure, success, warnings based on exception handling rules defined by the user. For example, failure in fully converting a file into another format or connecting to a source/destination sends a message, notifies users, alerts are shown in the dashboard for user to correct data in a workflow task form and resubmit the transaction if needed.
Adeptia provides multiple ways to handle exceptions. Please refer to the “Error Handling in Application Integration” for more information.
What is the process of promotion or migration of services from Development to Production?
Adeptia provides Migration Utility that allows users to implement, test and promote changes to the Production. Utility supports a graphical wizard to migrate all or specific services from your development environment to QA or Production. Refer to Migration guide that explains this process in detail.
How does the HL7 integration solution protect the work that is being done by the developers from unauthorized access or edits?
User access and permissions are key aspects of Adeptia’s HL7 integration solution. Each service contains permissions which the owner of the activity can control. User can share a service such as Mapping with other users in the group. User-based secure login and group level access maintains control on who views or edits any service within Adeptia. Administrators have full rights to create new users, suspend existing users and also can change ownership of activities from one user to another.