EDI Converter 2.14.9 Release
We’re pleased to announce version 2.14.9 of our EDI Converter.
This release focuses on completing support for the 837P standard, including FRM, PS1, SV5, and MEA segments, and improving the security of the API Server Docker image.
You can view all changes in GitHub diff format here.
Scroll down to openapi/components/schemas/model to see schema changes.
New JSON Objects and Fields
“FormResponse” Object (LQ and FRM Segments in 837P, Service Line Level)
Example (fragment; full JSON here):
"forms" : [ {
"formTypeCode" : "UT",
"formIdentifier" : "02.03B",
"responses" : [ {
"questionIdentifier" : "1",
"yesOrNoResponse" : "Y"
}, {
"questionIdentifier" : "2",
"textResponse" : "Our Response"
}, {
"questionIdentifier" : "3",
"dateResponse" : "2025-02-01"
}, {
"questionIdentifier" : "4",
"numberResponse" : 12.5
} ]
“DmeService” Object (SV5 Segment in 837P, Service Line Level)
Example (fragment; full JSON here):
"dmeService" : {
"procedure" : {
"subType" : "HCPCS",
"code" : "A4631"
},
"durationUnitType" : "DAYS",
"lengthOfMedicalNecessity" : 30,
"rentalPrice" : 50.00,
"purchasePrice" : 5000.00,
"billingFrequencyCode" : "4",
"billingFrequency" : "MONTHLY"
}
“Measurement” (Test Result) Object (MEA Segment in 837P, Service Line Level)
Example (fragment; full JSON here):
"measurements" : [ {
"categoryCode" : "TR",
"qualifierCode" : "R1",
"type" : "HEMOGLOBIN",
"value" : 113.4
} ]
Support for Purchased Service (PS1 Segment in 837P, Service Line Level)
We’ve added the following fields to the ServiceLine object:
purchasedServiceProviderIdentifier(EDI element:PS101)purchasedServiceChargeAmount(EDI element:PS102)
Improved Security of the API Server Docker Image
We now use a hardened base image for our API Server Docker image, with a minimal set of packages installed.
We’ve also updated dependencies to address known security vulnerabilities.
The container now runs as a non-root user with a restricted set of capabilities.
You can find more details here.
You can find the latest security reports and SBOM at the following links:
Improved AWS Lambda Function
Lambda function now accepts the isAboutOnly parameter in the request event. When set to true, the function will only return the version of the converter and the license information, without performing any conversion.
We’ve also added the ability to specify the output key in the request event.
We’ve also improved the function’s error handling and updated the documentation.
The Terraform files for the installation have been updated as well, you can find them here.
Codeset Changes
The Docker image has been updated to use the latest HCPCS, NDC, and ICD-10-PCS codes.
Bug Fixes
We’ve fixed a high-severity issue related to parsing MIA (Inpatient Adjudication) and MOA (Outpatient Adjudication) segments in 835 and 837 transactions. The parser did not correctly handle remark codes in these segments, so the resulting JSON lacked some of them.
How to Upgrade
API Docker container
If you are using Docker Compose, update the image tag to repo.datainsight.health/ediconvert:2.14 and pull the new image:
docker compose pull
The latest Docker Compose file is always available in our GitHub repo.
Without Docker Compose:
docker pull repo.datainsight.health/ediconvert:2.14
Check the version via the API:
curl http://localhost:5080/api/about
CLI tool
- Download the new version.
- Unzip and replace your existing installation files (including
libandconffolders). - Do not delete your license file.
- Run:
The output should include
ediconvert -Vediconvert 2.14.9.
EDI Parser for Java
Update your Gradle or Maven dependency:
implementation "hdi:edi:2.14.9"
AWS Lambda Function
Update the Lambda deployment:
aws lambda update-function-code --function-name <your function name> --zip-file fileb://./edi/build/distributions/ediconvert-lambda-2.14.zip
You can also use this Terraform file to update the function.