Skip to main content

v1.10.0 Release

· 3 min read
Founder and CEO

The top new feature in v1.10 is the extractor wizard. This brings forward our vision for making it easy to import common data (currently claims and eligibility data) in different formats into METL. Other exciting improvements include the beta version of our X12 837 EDI data loading, other data loading, and some important improvements to prepare for our fully open source future.

extractor Wizard​

With v1.10, we enable read-only access to all extractor claims and eligibility templates. This allows you to drop a file onto the web UI and view the extractor field mapping. You can't update the configuration at this time. The wizard is expected to allow for editable configuration in the v1.12 release, enabling rapid iteration to load data. The vision of the wizard is that teams will be able to get new data from a trading partner and configure and load it the same day.

Member matching performance fixes​

While member matching performance was great in our testing, it didn't fare so well on the larger databases of our customers. This release adds some fixes to improve performance including:

  • Query fixes: this is the biggest performance fix. The query change was HUGE. It went from 8 1/2 hours to 4 seconds. Bizarrely, there was no change to the functionality of the query. We had an OR condition in the query to get both scenarios. That OR condition caused it to go 8 1/2 hours. We switched it to two separate updates without an OR condition and it became 4 seconds.
  • Vacuum and analyze as needed: Early on, we added a vacuum and analyze to extractor after tables were updated. This fixed massive performance issues by ensuring that statistics were always up to date. Unfortunately, this came at the cost of running these operations after every load. This improvement changed this operation to only run after the number of rows in a table changed by enough to need a re-analyze. This shaves a few seconds off every load.

X12 EDI 837 data loading beta​

Improvements to 837 EDI loading. We've now extracted and loaded nearly 2000 different EDI files in our testing. Loads are working well, and we expect the prod release to be v1.11.

Data loads​

We've made some fixes to some data loads in 1.10 including a fix for ABA claims, and new data loading for Edison claims.

Other system improvements​

As we continue marching toward our full Open Source release, we're improving our systems to comprehend the capabilities we need to balance rapid iteration and a tighter feedback loop from our customers. Improvements this release include:

  • Python client CI and testing.
  • Database deploy CI fixes
  • JOSH (just one single history). This is the tool we've been needing to allow us to open source METL and be able to receive pull requests from the public repository and also push code from the internal repository. This gets us much closer to being able to fully Open Source METL.
  • METL archives with hashes. Rather than using dates, we're now using hashes. This ensures that we don't save the same exact file over and over to S3
  • Removed dependency on Microsoft Office email client which was causing the Web server for the Claims UI to not start

Release details​

Claims: Commit hash: aa9d00f

METL-deploy: Commit hash: 03358d9