Skip to main content
After ingestion, Ready Health collects documents, searches, and statements against each requirement. When those items are FULFILLED, you upload the compiled packet to the VMS.

Packets

A packet is one or more fulfilled artifacts grouped for a single VMS upload. Requirements share a packetGroup (for example clinical vs hr). GET /placement/{id} returns the packets on that placement:

Starting an upload

Call POST /vms/upload-packet with the packet id from the placement:
The call is accepted asynchronously (202):
Ready Health compiles the fulfilled documents in that group and writes them into the VMS placement (vmsPlacementRefId on the placement). Which VMS portal and how the files are attached is part of the integration config — you only pass the packet id.

Tracking status

Poll GET /placement/{id}/package-status. Each packet includes status, uploadedAt, and compiledFileId once those exist. Typical path:
If status is FAILED, inspect the placement requirements (rejected / expired items), fix them, and call POST /vms/upload-packet again with the same packet_id.