v1.13 Release
Our January release is primarily filled with new capability preparation. We're building out the ability to load Rx data to the database. We're also working on our Extractor UI to dramatically reduce the time it takes to translated data files into the METL schema. And, we're building the METL domain specific language (DSL) to make it easier to handle contract repricing, accumulators, payment integrity, and more.
New features and improvements
Preparation for new Rx data loading
We've done a lot of work to prepare for loading prescription drug data to the database.
- Extractor templates moving to the database
- Rx Schema
- rename Go struct fields
- update DB schema
Jobs UI
The Jobs UI has turned out to be an very helpful tool to easily view and troubleshoot load issues. We continue expanding and improving it with:
- Enable searching for only failed jobs
- Fix paging
Claims repricing workflow improvements
Enable adding new claim status through API
Working on METL Domain Specific Language
METL DSL MVP. This will unlock capabilities for contracts, accumulators, payment integrity and much more.
Enterprise tenant deployment
We've enabled the METL web UI for our enterprise tenants.
Other various enhancements
- Switch to govalues/decimal. We now use this for all decimals instead of the previous
decimalpackage we used which took much more memory. - Add
member_canonical_id_chosento views so we can take advantage of patient matching data - More line item categories for grouping for better reporting
- Rename columns with "_id" that aren't key columns for clearer usage
- Make patient matching more deterministic for better comparison and consistency
- Use
claim_numberas the standard claim number instead ofpayer_claim_numberfor better clarity and consistency.
Testing and Deployment
- Automated Python package publishing via GitHub Actions
- Fixes to make it easier to release Python package