Schema Care
BlogSign inStart free

APIs, FHIR and Integration

This category is for the developers who wire extracted data into other systems. It covers what to expect from a medical document extraction API, how extracted fields map to FHIR resources, HL7 messages and X12 835 and 837 files, how to design a JSON schema with confidence scores and source locations, how to connect results to an EHR, and how to test safely with synthetic documents. Read "Medical Document to FHIR: A Field Mapping Guide" first, then "JSON Schema for Medical Documents: Fields, Scores, Sources".

  1. Code System Mapping in Extracted Data

    How code system mapping in extracted data works for ICD-10, CPT, HCPCS and CARC codes, and how to normalize dates and amounts before data reaches other systems.

    October 5, 2026codesicd-10normalizationdata

  2. The FHIR ExplanationOfBenefit Resource for Developers

    How the FHIR ExplanationOfBenefit resource is structured, how it relates to the Claim resource, and how extracted EOB fields fill its items and adjudications.

    September 28, 2026fhireobinteroperability

  3. FHIR Bulk Data Export: What Developers Should Know

    How FHIR bulk data export works: the $export kickoff, async status polling, NDJSON output files and backend auth, and when a bulk export is the wrong tool.

    September 28, 2026fhirbulk datandjsonsmart

  4. C-CDA vs FHIR: Which Format Fits Clinical Document Data

    C-CDA vs FHIR for clinical document data: how each format is structured, what receiving systems accept, and how to choose between them for extracted fields.

    August 19, 2026c-cdafhirclinical documents

  5. Confidence Scores in API Responses: Schema and Use

    How confidence scores in API responses should be shaped per field, paired with page coordinates, and used in code to route uncertain values to review.

    August 15, 2026apiconfidencereviewjson

  6. X12 275 Claim Attachments: How the Transaction Works

    How X12 275 claim attachments work: the BIN segment that carries the file, the PWK link back to the 837, the 277 request, and which payers accept them.

    August 12, 2026275x12ediattachments

  7. Insurance Card OCR API: The Response Fields to Expect

    What an insurance card OCR API should accept and return: front and back images in, member, group, payer and Rx fields out, each with a confidence score.

    July 17, 2026insurance cardapiocrjson

  8. Batch Processing Medical Documents via API

    Plan batch processing medical documents via API: input formats, upload limits, retries with idempotency keys and tracking hundreds of jobs without duplicates.

    July 1, 2026apibatchidempotencyuploads

  9. Medical Document to FHIR: A Field Mapping Guide

    Map fields extracted from a medical document to FHIR resources, with a resource table for EOBs, claims, lab reports and intake forms, and the gaps to plan for.

    June 20, 2026fhirintegrationmapping

  10. EOB API: What an Explanation of Benefits Endpoint Returns

    What an EOB API should return for each claim and service line, with a sample JSON response covering allowed amounts, plan payments and remark codes.

    June 11, 2026eobapiremittance

  11. FHIR DiagnosticReport and Observation for Lab Data

    How FHIR DiagnosticReport and Observation resources hold lab data, with a worked example that turns one extracted lab result into valid resources.

    May 30, 2026fhirlab resultsinteroperability

  12. FHIR QuestionnaireResponse for Intake Forms, Step by Step

    Turn paper intake forms into a FHIR QuestionnaireResponse: link IDs, answer types for checkboxes and dates, and how to extract Patient and allergy resources.

    April 5, 2026fhirquestionnaireintake forms

  13. Lab Report API: The Fields and Response Shape to Expect

    What a lab report API should return for each test: name, result, units, reference range and flag, shown in a sample JSON response with edge cases to handle.

    April 2, 2026lab reportsapidata model

  14. Webhooks for Document Processing: A Developer Guide

    Set up webhooks for document processing: async job states, payload design, signature checks and authentication, and a receiver that survives retries.

    March 19, 2026webhooksapisecurityasync

  15. X12 837 Generation From Extracted Claim Data

    Plan X12 837 generation from extracted claim data: the 837P and 837I loops, which fields map where, and the validation checks to run before a file goes out.

    January 13, 2026837x12ediclaims

  16. JSON Schema for Medical Documents: Fields, Scores, Sources

    Design a JSON schema for medical documents that carries each field's value, confidence score and source location, with a sample schema to adapt and version.

    January 2, 2026json schemadata modelintegration

  17. Medical OCR API Example in Python, Start to Finish

    A medical OCR API example in Python: upload a fictional EOB, poll or receive a webhook, parse the JSON fields and flag low-confidence values for review.

    December 21, 2025pythonapiocrconfidence

  18. Mapping Extracted Fields to an EHR, Step by Step

    A step-by-step plan for mapping extracted fields to an EHR: the integration options, a field mapping table and the checks that keep bad values out of charts.

    October 29, 2025ehrfhirfield mappingintegration

  19. FHIR Coverage Resource From Insurance Cards, Field by Field

    Build a FHIR Coverage resource from insurance cards: which element holds member ID, group, plan, Rx numbers and copays, and what to do when the card is silent.

    October 13, 2025fhircoverageinsurance cardus core

  20. EHR Integration vs RPA for Data Entry

    EHR integration vs RPA for data entry from documents: cost, reliability, maintenance and audit trail compared, with a decision table for your team.

    September 26, 2025ehrrpaintegrationdata entry

  21. X12 835 Parsing: Segments, Loops and Sample Code

    A practical guide to X12 835 parsing: the envelope, loops and segments that carry payments and adjustments, with sample code and the edge cases that break it.

    June 25, 2025x12835remittance

  22. REST API vs SFTP for Healthcare Document Intake

    REST API vs SFTP for healthcare document intake: a side-by-side comparison of latency, error handling, security and setup cost to help you pick one.

    June 9, 2025apisftpintakeintegration

  23. Testing With Synthetic Medical Documents

    How to start testing with synthetic medical documents: build a fictional test set, label ground truth, and measure an extraction pipeline without real PHI.

    May 20, 2025testingsynthetic dataextraction

  24. HL7 v2 vs FHIR for Extracted Document Data

    HL7 v2 vs FHIR for sending extracted document data: message and resource structure compared side by side, and when each one fits your receiving system.

    May 8, 2025hl7fhirinteroperability

  25. What a Medical Document Extraction API Should Do

    What a medical document extraction API should accept and return, from OCR to structured fields, plus a vendor-neutral checklist for evaluating one.

    October 25, 2024apiextractionevaluation