Skip to main content

v1.15 Release

· 5 min read
Founder and CEO

Our June release turned into a much bigger release than we anticipated.

New Features and Improvements​

Exporter Service​

The Exporter Service is a new service that allows data export from the database in a variety of formats. The initial version of the Exporter Service supports exporting claims data in CSV format, but we have plans to expand the capabilities of the Exporter Service in future releases. The Exporter Service is designed to be flexible and extensible, so we can easily add new export formats and new data types in the future.

The Exporter service ships with a new scheduler which allows us to schedule exports on a daily, weekly, monthly, or various other time windows. If you've ever worked with a cron job on a 'nix system, you'll be very familiar with the scheduling flexibility.

The data that is exported is only limited by your SQL querying skills. If it can be queried in SQL, it can be exported. This is the natural bookend to the load wizard we've been working on and makes it just as easy to get data out as it is to get it into METL.

The UI for the Exporter will be coming in a future release.

Scheduler Service​

As a part of the launch of the Exporter Service, we've added a new scheduler service. This will allow us to schedule regular tasks. It's being used to schedule Exports, but we'll soon be switching our jobs such as database backups, file reload tasks and more to the scheduler service. This will allow us to build in more and more automation right into the METL platform. Previously, we were relying on cloud task automation to accomplish this, but now it'll be built directly into METL for greater flexibility to end users.

The UI for the Scheduler will be coming in a future release.

Extractor UI​

The Extractor UI got some more polish this release and more capability to prepare it for editing. This included improved and more consistent error handling, cleanup to make it look more polished, and moving all the UI capabilities in extractor UI into individual components for easier maintainability. We're excited to add editing capability to the July release.

AI additions​

This release marks our first steps into AI development. We added our project-level configuration, added several Claude Skills and dove head first into AI development. We found some efficiencies in the process and lots of drawbacks to the process. We had at least 2 weeks of delays this release as we worked to adjust the code to our style. In general, coding went marginally faster, but review went significantly slower than prior releases. We expect to see this continually improve as we adjust to the new paradigm of development.

Web UI updates​

We improved Patient matching API performance.

Jobs redesign​

One of the consistent pieces of feedback we've received is that the METL UI needs to make more information available about the status of data loads. If a file is dropped in that doesn't match a regex, nothing is ever shown in the UI. With v1.15 we've completely redesigned the way we log information. Everything does not have to be associated with a "release" record (and ultimately load to the database). This allows us to log every time something happens with extractor and csvloader, even if they fail in unexpected ways.

In a subsequent release, we will introduce updates to the jobs UI for 3 different use cases:

  1. The lowest level view providing a list of all jobs of any type occurring in the database in an auto-updating stream. This includes ETL jobs like extractor and csvloader, but it also includes exporter jobs as well as HTTP and any future type of job we add support for. This will be the UI to use for seeing a running view of everything happening for up-to-the minute troubleshooting.
  2. A medium-detail view of jobs grouped by ETL jobs. This is the current view in the jobs UI.
  3. A higher level jobs dashboard. This will make it possible to see multiple instances of jobs grouped together in a clean dashboard showing the status of each group. For example, if there have been 100 loads run for "ABC TPA Claims", you'll see a single card with "ABC TPA Claims" that shows Green if all 100 jobs have been successful. If any file for "ABC TPA Claims" didn't succeed, the card would be red. If there are jobs waiting to complete for "ABC TPA Claims" it would be yellow. That way, at a glance you can see what's happening per load without having to drill-down. We expect it will make it much easier to quickly see what's happening across a large list of load, export, and other types of jobs.

New data loads - adding prescription drugs!​

We added several new data loads this release, and also added our first data load for prescription drugs. We're excited to have full support for prescription drugs and expect to add many new loads in the future.

View improvements​

  • line_item_reporting_view - added date_of_birth and medical_plan_name

Repricing improvements​

We continue to add new capabilities to our My Price Health repricing engine for our enterprise clients. New capabilities include:

  • Better support for modifiers and provider types
  • Inpatient CBSA fallbacks

METL DB Release on GitHub

METL-deploy on GitHub