EDI Converter 2.14.7 Release

We’re pleased to announce version 2.14.7 of our EDI Converter.

New JSON Objects and Fields

“ConditionsIndicator” Object (CRC Segments in 837P and 837I)

All CRC segments are parsed into an array of “ConditionsIndicator” objects with the appropriate category code.

Professional claims can have these objects at the claim and line level. Institutional claims can have them only at the claim level (EPSDT referral).

Example (fragment; full JSON here):

  "conditionsIndicators" : [ {
    "categoryCode" : "07",
    "category" : "AMBULANCE_CERTIFICATION",
    "yesOrNoCondition" : "Y",
    "conditionCodes" : [ "04", "06", "09" ]
},

Object schema

Ambulance Transport Info (CR1, 837P only)

Example (fragment; full JSON here):

  "ambulanceTransportInfo" : {
    "patientWeight" : 275,
    "reasonCode" : "A",
    "reason" : "NEAREST_FACILITY",
    "transportDistance" : 21,
    "stretcherPurposeDescription" : "PATIENT IMMOBILIZED"
  }

Object schema

Spinal Manipulation Info (CR2, 837P only)

Example (fragment; full JSON here):

  "spinalManipulationInfo" : {
    "conditionCode" : "A",
    "description" : "CHRONIC PAIN AND DISCOMFORT"
  }

Object schema

DME Certification (CR3, 837P line-level only)

Example (fragment; full JSON here):

  "dmeCertification" : {
     "certificationTypeCode" : "I",
     "duration" : 99
   }

Object schema

Other JSON Changes

  • New “lastCertificationDate” field (DTP*461) for 837p transactions (ServiceLine object)
  • New “certificationRevisionDate” field (DTP*607) for 837p transactions (ServiceLine object)
  • Support for patient identifier (SSN) in the PAT segment (when the patient is not a subscriber)
  • The API server now provides descriptions for the Place of Service codes.

Critical Bug Fix

We’ve fixed a critical bug related to the place of service code in 837P transactions. In some instances, codes that start with “0” can be transposed.
For example, the code “02” can be parsed as “20”.

We recommend upgrading to this version as soon as possible to avoid data corruption.

The place of service code can be found in the “facilityCode” object with the “PLACE_OF_SERVICE” type:

  "facilityCode" : {
    "subType" : "PLACE_OF_SERVICE",
    "code" : "02"
  },

CLI Command Completion

You can now install command completion for the CLI tool (Bash and zsh only for now).

Download the completion file and follow the instructions here to install it.

How to Upgrade

API Docker container

If 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

  1. Download the new version.
  2. Unzip and replace your existing installation files (including lib and conf folders).
  3. Do not delete your license file.
  4. Run: 
    ediconvert -V
    The output should include ediconvert 2.14.7.

EDI Parser for Java

Update your Gradle or Maven dependency:

implementation "hdi:edi:2.14.7"

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.