API for the Exchange of Medicinal Product Information (APIX)
0.1.0 - ci-build International flag

API for the Exchange of Medicinal Product Information (APIX), published by HL7 International / Biomedical Research and Regulation. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/APIX---API-Exchange-for-Medicinal-Products/ and changes regularly. See the Directory of published versions

Document Streaming

Page standards status: Informative

Document Streaming

How APIX modernizes document exchange by moving from bulk portal uploads to a Netflix-style "streaming" metadata model.

The "DVD Delivery" Problem

Today's regulatory portals operate like the old mail-order DVD business. When a company submits an application, they package hundreds or thousands of PDFs into a massive ZIP file (eCTD) and upload it via a portal.

  • The company's system is locked up pushing gigabytes of data.
  • The regulator's system is locked up receiving, virus-scanning, and storing it.
  • Reviewers must download the entire massive package just to find and read a single 5-page clinical summary.
The APIX Solution: The Netflix Model

APIX changes this paradigm by treating documents like a modern streaming service treats movies. Instead of forcing the regulator to download the whole "DVD box set" upfront, APIX separates the catalog from the content.

1. The Catalog (DocumentReference)

The company sends lightweight metadata — titles, CTD sections, file types, and unique identifiers. The regulator's system indexes this instantly. This is the "Netflix menu."

2. The Content (Binary)

The actual heavy PDF/JSON files are stored securely on the FHIR server. They are only "streamed" (downloaded) at the exact moment a human reviewer clicks to read them.

Why This Matters for Business Leaders

⚡
Sub-second Processing

Because the regulator only processes the lightweight "catalog" during the initial submission, wait times drop from hours to milliseconds.

💾
Drastic Cost Reduction

Regulators no longer need massive, expensive staging servers to hold gigabytes of ZIP files while they are unzipped and scanned.

🎯
Precision Updates

When answering a regulatory question, the company only sends the specific new document, rather than re-uploading an entire sequence folder.

🔍 Technical Deep-Dive: For the exact sequence of how client systems upload the Binary and then link it via the DocumentReference, see the Post-then-Link section of the Architecture guide.