メインコンテンツへスキップ
このページの日本語版はまだありません。以下は英語の原文です。
Upload a report on the web client’s Data page. Mirobody keeps the source file and extracts the readings it can identify, including printed units, reference ranges and report dates.

​
Supported documents

Legacy .xls, .xlsb, .doc and .ppt files are not supported. Convert them to a supported format first. Raw genotype exports follow a separate genetics workflow.

​
Upload and review

  1. Select the person’s record and upload the document.
  2. Wait for both upload and extraction to finish. A stored file can still have failed extraction or contain no usable readings.
  3. Review the extracted date, values, units and reference ranges against the original. Correct uncertain results before relying on them.
  4. Ask a question or open the indicators view. Citations lead back to the source.
Text tables are read locally where possible. Other content uses the configured models. To keep images local, follow the local or hybrid instructions in Choosing a Model.

​
API integration

Use POST /files/upload for REST uploads, or /ws/upload-health-report for progress events. WebSocket clients must wait for extraction_completed; upload_completed only confirms file storage. Requests require authentication and permission to write to the target record. The deployment’s /docs page lists current request schemas. If a file is stored but no readings appear, check the extraction status, model configuration and ENABLE_INDICATOR_EXTRACTION setting. Interface examples, limits and error formats are in the file-processing reference.