BCDA V3 – Clarification on FHIR Mapping for CLM_PROD_TYPE_CD (CCLF vs. BCDA V3)

43 views
Skip to first unread message

Ashvani goyal

unread,
Sep 10, 2026, 10:00:07 AM (14 days ago) Sep 10
to Beneficiary Claims Data API (BCDA) Community

Hi BCDA Team,

We would like to request clarification regarding the mapping of CLM_PROD_TYPE_CD (Claim Product Type Code) between the CCLF file and BCDA V3.

As per the CCLF Version 39 documentation, CLM_PROD_TYPE_CD is a one-character field used to classify the diagnosis category. The documented values include:

  • E – Accident diagnosis code
  • 1 – First diagnosis E code
  • D – Other diagnosis code

However, in BCDA V3, we are receiving diagnosis type values such as:

  • principal
  • admitting
  • other

We are currently following the following FHIR mapping for this field:

FHIR Path: ExplanationOfBenefit.diagnosis.type.coding

Could you please clarify the following:

  1. Is ExplanationOfBenefit.diagnosis.type.coding the correct FHIR path to use for mapping CLM_PROD_TYPE_CD?
  2. How should the BCDA V3 values such as principal, admitting, and other be mapped to the corresponding CCLF CLM_PROD_TYPE_CD values (E, 1, D)?
  3. Is there any additional FHIR field or coding system that should be considered to distinguish accident diagnosis, first diagnosis E-code, and other diagnosis?
  4. If the BCDA V3 values do not have a direct one-to-one mapping with the CCLF values, could you please provide the recommended mapping logic for generating CLM_PROD_TYPE_CD from BCDA V3 data?

We want to ensure that our BCDA V3 → CCLF transformation follows the expected CMS/BCDA mapping and does not introduce differences from the existing CCLF output.

Please provide the recommended mapping or any relevant documentation for this field.

Thanks,
Ashvani Goyal

Ashvani goyal

unread,
Sep 16, 2026, 8:53:54 AM (8 days ago) Sep 16
to Beneficiary Claims Data API (BCDA) Community
Hi Team,

We are still awaiting for your response.

Thanks
Ashvani Goyal

Beneficiary Claims Data API (BCDA) Community

unread,
Sep 22, 2026, 10:53:07 AM (2 days ago) Sep 22
to Beneficiary Claims Data API (BCDA) Community

Hi Ashvani ,

Thank you for your question about the mappings of CLM_PROD_TYPE_CD!

We were able to confirm that ExplanationOfBenefit.diagnosis.type.coding is the correct FHIR path to use for mapping CLM_PROD_TYPE_CD. After checking with our upstream data source, the Beneficiary FHIR Data (BFD) Server, the values of CLM_PROD_TYPE_CD are translated into FHIR diagnosis type codes based on https://terminology.hl7.org/7.3.0/en/CodeSystem-ex-diagnosistype.html and https://hl7.org/fhir/us/carin-bb/STU2.2/en/CodeSystem-C4BBClaimDiagnosisType.html. 

The mapping from CLM_PROD_TYPE_CD to FHIR Diagnosis Type is as follows:

1: externalCauseOfInjury
A: admitting
D: other
E: externalCauseOfInjury
P: principal
R: patientReasonForVisit

If you find any deviations from this mapping behavior, please reach out to us and we can further investigate any examples.

Thank you,

The BCDA Team

Reply all
Reply to author
Forward
0 new messages