Care Evolution Logo Care Evolution

Unlock maximum insight from uncoded and free text clinical terms buried in digital health records

Varying and uncoded clinical terms require standardization for interpretation to be reliable and accurate.

The Convert API’s terminology standardization links ontologies which can then be enriched with industry code sets.

HDLc SerPl Elph-mCnc HDL Cholesterol LDL Direct Direct LDL Cholesterol LDL-CHOLESTEROL HDL-P (Total) LDL Chol Calc (NIH) Cholesterol.in HDL HIGH-DENSITY LIPOPROTEIN (HDL) LDLc SerPl-mCnc LDL Chol. (Direct) LDL Chol-Mayo LDL SerPl-sCnc Real-LDL-C HDL SerPl-sCnc LDL Cholesterol Calc Total Cholesterol SUM TOTAL CHOLESTEROL TRIGLYCERIDES (REFL) HDL SerPl Qn Triglycerides. (DC) Triglycerides (QUEST) (DC) Triglycerides (Labcorp) Total Cholesterol POC Triglycerides measurement (procedure) (DC) TRIGLYCERIDE POWERWORKS Finding of triglyceride level (finding) CARDIO IQ(R) TRIGLYCERIDES Triglyceride TR HDL-CHOL Triglyceride level – finding TOTAL CHOL TOTAL CHOLESETEROL LDL med SerPl Qn Triglyceride POC HDL POC LDL POC LIPID Panel 
 (HDL, LDL, Cholesterol, Triglycerides) Codes for LIPID Panel (HDL, LDL, Cholesterol, Triglycerides) Different codes for LIPID Panel (HDL, LDL, Cholesterol, Triglycerides) fan out from center

To maximize utility across applications and systems, uncoded, proprietary-coded, or free text source terms from patient records are mapped to industry code sets like ICD-10-CM, SNOMED, and LOINC®.


Quantifiable enhancements to your clinical data

Example of the amount of codes added to patient records from a 110,000 member health plan over 18 months:

Codes Added by the Convert API
Codes contained in original records
0% 0
0% 0
Example of the amount of codes added to patient records from a 110,000 member health plan over 18 months Bar charts comparing codes Added by the Convert API verses codes contained in original records 0% 0 Example of the amount of codes added to patient records from a 110,000 member health plan over 18 months Bar charts comparing codes Added by the Convert API verses codes contained in original records

Power more accurate and efficient medical record reviews

The Convert API drastically reduces the burden of medical record reviews by consolidating duplicate records into a clean and organized patient record with summaries for conditions, diagnoses, procedures, tests and medications so reviewers know where to look.

Use data from diverse sources and formats across applications

Make data work with your existing tools and systems without costly upgrades. The Convert API transforms your files into file formats like FHIR(R4), CDA, or PDF, ensuring high ingestion success and usability across systems.

Liberate Data 
 From Any Source EHR Claims Clinic Labs HIEs Convert API Medications Labs Vitals Claims Diagnoses Procedures Encounters Organize ICD10 HCPCS CPT LOINC SNOMED RxNorm CVX Standardize File Format
Conversion PDF HTML </> CDA OMOP NEMSIS (R4) BUNDLES COMBINED
 Use Cases Risk Stratification CMS Star Ratings HCC Scoring Gaps in Care Medical Record Reviews + Life Insurance
Claims & Underwriting Care Quality & Coordination 1.0 The Convert API transforms your files into a file format like FHIR(R4), CDA, or PDF, ensuring high ingestion success and usability across systems. The Convert API liberates and transform data for a variety of use cases

Uncover insights hiding in your patient data

Contact us to get started

The Convert API is used throughout the healthcare system to power more informed decisions across applications, departments and organizations.

Read more about the industries we serve:

Real-world patient data transformation success stories

  • A large payvider streamlines patient records to improve care quality and coordination

    Concerned about the time and resources needed to ingest and aggregate direct clinical feeds from multiple sources, a large payvider (payer-provider partnership) deployed CareEvolution’s APIs, including the Convert API, to ingest, aggregate, and enrich patient data from various sources to produce a comprehensive, up-to-date patient record. Providers and members now have ‘real-time’ access to lab and imaging reports, medication details, claims, and clinical encounter information in their workflow. Analytically ready data streamlines performance improvement efforts and reporting. The platform also facilitates real-time acute and post-acute care tracking, generating FHIR notifications to alert the care management team upon admission or discharge to drive more efficient care coordination.

  • A well known national Health plan Merges Enriched Records for 46 million members to enhance risk adjustment and care management

    A well-known national health plan adopted CareEvolution’s APIs to create consolidated and enriched master patient records for its 46+ million members, connecting over 2,800 providers, 240 data sources and 7.5 billion claims. The organization successfully leverages the platform for AI, machine learning, risk adjustment, quality program development, care management, member engagement, collaboration across benefit offerings, and clinical trials.

  • A health tech vendor faced the challenge of managing and consolidating extensive medical histories for patients

    This health tech company ingests large volumes of patient records from over 600,000 providers, with individual files averaging 500 pages and often spanning 30 or more CDA documents, sometimes reaching as high as 700 CDAs. To streamline the aggregation and eliminate redundant content, they adopted the Convert API. By using the Convert API, they dramatically reduced file sizes and page counts while maintaining data integrity. For instance, one patient’s medical record, originally 7,342 pages, was consolidated into a single, de-duplicated 600-page PDF. This transformation optimized workflows, improved usability, and significantly enhanced document management efficiency.

  • A patient data aggregator creates enriched master patient records in multiple output formats for use across departments and applications

    Built to serve multiple patient data use cases across operational departments, this health technology company focuses solely on creating a rich network of patient data for multiple purposes across numerous markets. They needed a partner with a highly scalable API that could take multiple patient records, harmonize them, normalize code sets and medications, and make them available in multiple output formats from FHIR, CDA, to OMOP. It was also critical that their partner offer modern “software” SaaS pricing vs high historical costs associated with manual processes. They sought to eliminate costs and enable mass adoption of harmonized, cleansed patient data.

Developers and healthcare IT teams use the Convert API to:

radiant arrow icon

Convert to any file format including FHIR, CDA, HTML, X12, HL7, PDF, NEMSIS, FHIR(R4) and OMOP

radiant consolidation icon

Consolidate & dedupe records into FHIR bundles to form a single patient record

radiant check mark icon

Add standard terminology and code reference systems to applicable clinical terms in the record

How the Convert API enriches an uncoded condition by adding SNOMED & ICD-10 codes

{
   "code": "Hepatitis B Vaccine",   
"display": "Hepatitis B Vaccine"
 } received from Source Uncoded condition "Hepatitus B"
from Orchestrate Standardized SNOMED & ICD10 codes Standardized data elements usable for numerator compliance   { 1 ⌄    "coding": [ 2 ⌄       { 3 ⌄ "http://snomed.info/set" "system" : , 4 "code" : " ", 5 16584000 " "display" : 6 Administration of vaccine product containing only Hepatitis B virus antigen (procedure)", "mapMethod" : " ", NLP 7        }, 8      { 9 ⌄ 10 "system" : " https://www.cms.gov/Medicare/Coding/ HCPCSReleaseCodeSets " , "code" : " ", 11 Z9731 12 "display" : " HEPATITIS B VACCINE ", "mapMethod" : " ", 13 ExactName 14       } 15     ] 16   } Convert API enriches an uncoded condition by adding SNOMED & ICD-10 codes Shows initial code and the resulting code processed by the Convert API
Untitled Document

Example of original EMR C-CDA file with uncoded clinical terms enriched with codes by the Convert API

Data Type Source Code System Raw Value (EMR CCDA) Codes Added by the Convert API
Data TypeImmunization Source Code SystemCVX Raw Value (EMR CCDA)08 (HEPATITIS B 0-19 YRS./ENGERIX B 08 ) Codes Added by the Convert API49610 (RXNORM) 08 (CVX)
Data TypeLab Source Code SystemEPIC Proprietary Raw Value (EMR CCDA)125306 (CHLAMYDIA TRACHOMATIS IGM ABS) Codes Added by the Convert API134256004 (SNOMED)
Data TypeProcedure Source Code SystemFree Text Raw Value (EMR CCDA)GI-COLONOSCOPY SCREENING (LVL4) Codes Added by the Convert API73761001 (SNOMED)

How the Convert API helps IT Teams

  • Automatically accommodates wide variations across sources such as Epic, Allscripts, Athena, Cerner and more

  • Handles errors with high ingestion success rates, with warnings instead of failures

  • Extracts dates and times from non standard formats

  • Handles non-standard and proprietary templates from all CDA types

  • Continuously updates API to handle changes across industry sources

  • Self service APIs integrate seamlessly into existing tech stacks

How the Convert API transforms data

CDA to FHIR Example 1: Convert API CDA CDA CDA CDA CDA CDA CDA CDA CDA CDA (R4) (R4) (R4) (R4) (R4) (R4) (R4) (R4) (R4) (R4) File conversion chart 1 Example 1: CDA to FHIR
Multiple source format inputs to FHIR bundles, combined into a single patient FHIR bundle converted to multiple outputs Example 2: CDA CDA CDA CDA Convert API (R4) (R4) (R4) (R4) (R4) (R4) (R4) (R4) Convert API BUNDLES COMBINED
 PDF PDF CDA File conversion chart 2 Example 2: multiple source format Inputs to FHIR bundles, combined into a single patient FHIR bundle converted to multiple outputs
Mc ultiple CDAs, to FHIR bundles, ombined into a single FHIR bundle, converted to OMOP Example 3: CDA CDA CDA Convert API (R4) (R4) (R4) Convert API COMBINEBUNDLES BUNDLES COMBINED
 Convert API OMOP File conversion chart 3 Example 3: multiple CDAs, to FHIR bundles, combined into a single FHIR bundle, converted to OMOP

Example of how to use Python to convert a CDA document to FHIR (R4) using the Orchestrate Convert API.

Why use CareEvolution’s Convert?

  • Enriched Clinical Data

    The Convert API parses and organizes your clinical data, standardizes terminology and adds coding from standard code reference systems, and then outputs it in your desired format.

  • Fast & Flexible Architecture

    Modern, stateless, cloud-native architecture fits seamlessly into any existing workflow. Without any changes to data infrastructure or architecture, calling the Convert API can be done in a matter of hours.

  • Secure

    CareEvolution’s Orchestrate APIs meet stringent HIPAA-compliance standards and are HITRUST certified. Our security program is based on the National Institute of Standards and Technology (NIST) SP 800 53 Rev 5 at the FISMA Moderate and Privacy baselines. We regularly undergo assessments from a Third Party Assessment Organization (3PAO).

  • Proven

    Convert has been developed and refined by CareEvolution over the past 15+ years and is used by a broad range of payers, health systems, and health tech companies throughout the US healthcare system.

Enable better interoperability with a seamless flow of enriched information across healthcare systems.

Different healthcare providers, systems, or applications often use incompatible formats for effective interoperability. Converting between formats streamlines the process of data exchange, integration, and aggregation in the healthcare ecosystem. The Convert API supports the following operations:

Conversion to FHIR

Convert FHIR bundles to other formats

Other conversions

Convert experience

  • 15+ Years experience with healthcare data formats
  • 200M+ Lives

Trusted by leading healthcare organizations

  • Clover Logo
  • Trinity Logo
  • <Clareto Logo
  • ECU Logo
  • Avaneer Logo
  • Camden Logo

Learn more about the Convert API.

Complete a clinical data diagnostic report today

Up to 1,000 CDAs can be assessed complimentary

Contact us to get started