Consistency playground
Run an example packet or upload documents, then check the marked evidence.
The Consistency tab compares documents in one packet. Your organization must have Consistency enabled to see the tab. Start with an example packet to see how the answer points back to the pages.
Run an example packet
The playground has four steps. The progress header shows one step at a time and lets you return to completed steps.
flowchart LR
A["1 Add documents"] --> B["2 Review"] --> C["3 Run"] --> D["4 Answer"]- Open Playground, then select the Consistency tab.
- At Add documents, select Try an example packet. The example pop-up groups packets by type and separates examples with a problem from examples with an honest similarity. Each card shows Has issues or Clean.
- Select an example. Read its story, documents, and What to look for list. Selecting an example does not run it. Click Use this example.
- At Review, check the documents and story. Click Run the check.
- At Run, wait for the check to finish. You can cancel or retry a failed run without choosing the packet again.
- At Answer, read the result and open a marked problem to compare the pages. Open Technical details for coverage and unavailable checks.
flowchart LR
A["Example pop-up<br/>choose a packet"] --> B["Story and document preview"] --> C["What to look for"] --> D["Use this example"]The example documents are synthetic. Their page previews load in your browser.
Three example stories
| Example packet | What to look for |
|---|---|
| Desmond's note describes Marisol | Riverside records a right-side spine injection for Desmond on Mar 24. Desmond's note repeats Marisol's age, female pronouns, and past surgery. Copied text across two patients. Desmond's note describes a woman and her hysterectomy. His claim bills the left side while the note says right. |
| The bill total is $137 too high | Calla receives an estimate and a final bill for water damage to her home. The bill lists $1,580.06 in work and tax but prints $1,717.06 as the total. The invoice total is $137 higher than its listed work and tax. |
| A ring has two different stone weights | Corwin's ring is listed in an appraisal, a lab report, a receipt, and an insurance record. The appraisal and lab say 13.88 carats; the receipt says 1.85 for the same stone number. The stated 13.88-carat weight is implausible for the measurements. The receipt's 1.85 carats conflicts with the other pages. |
These stories are leads for review. A person checks the source documents and decides what happened.
Upload your documents
At Add documents, drag files into the box or click Choose files. The request-based default is 2 to 4 documents and up to 40 pages total. For organizations with background jobs enabled, the default is 20 documents and 500 pages. History mode permits a one-document packet. The playground reads the live max_documents and max_pages values from your organization's configuration, and reports limit errors at the Review step. Accepted files are PDF, PNG, JPEG, or TIFF. TIFF files can be analyzed but cannot be previewed in the browser.
The browser counts PDF pages and treats PNG and JPEG files as one page each. It cannot count TIFF pages. The service checks the final count. The Review step shows a live usage estimate for counted pages at 6 SCU per page. If a page count is unavailable, the estimate is a lower bound. For example, four counted pages cost 24 SCU. The service bills a delivered packet once.
Under Advanced (for API users), you can add claim lines as JSON. The playground assigns d1, d2, and later IDs in upload order. Most reviewers can leave this field empty.
When playground history is off, the following privacy statement applies. Files are uploaded to our service for analysis. History is off in this playground, so later packets are not compared with this one. Sealed replay evidence can retain coded document data. It does not retain readable document text. When playground history is enabled for your organization, Settings > Consistency controls comparison with earlier playground packets. API history is separate. See Consistency privacy and billing.
Read the three result levels
| Answer | Meaning | Next step |
|---|---|---|
| Needs review | One or more problems need a human check. Coverage can also be incomplete. | Compare the marked passages and verify the source documents. Retry any unfinished checks. |
| Could not finish checking | No problem was shown, but one or more checks did not finish. | Retry the packet or check the unfinished work by hand. |
| No problem found in completed checks | The completed checks found no problem. | Keep the result with the case and continue human review. |
A status list under the top line says what the run covered: whether every section was compared (for example "Coverage incomplete: 10 of 12 sections were compared"), whether history was used, and any part of the engine that was skipped or is not available yet, such as dollar amounts.
A quiet result does not certify the packet. Check coverage under Technical details, especially if a page or section could not be read. The result includes a Copy review summary button.
The API uses summary.headline and summary.sentence to describe visible problems. Each visible finding can include headline and what_to_check. Those fields do not report incomplete checks. To apply the three levels in your app, read status.coverage.complete and each document's coverage_complete alongside the findings. See the packet response.
When a run fails
| Code | What to check |
|---|---|
attestation_required | Your organization has not stated whether it is a HIPAA covered entity or business associate. |
baa_required | Your organization is a covered entity or business associate and the BAA flag is not set. The playground passes the same gate as the API. |
too_many_documents, too_many_pages | More than your organization's displayed limits (20 documents or 500 pages by default with background jobs enabled). |
unsupported_file_type | A file is not a PDF, PNG, JPEG, or TIFF. |
content_type_mismatch | A file's contents do not match its type. |
async_unavailable | The packet could not run inside the request and async runs are not open to your organization. |
Consistency costs 6 SCU per page (an image document counts as one page). When you add files, the tab shows the packet's price before you run it, for example 4 pages x 6 SCU = 24 SCU. See Consistency Privacy And Billing.
A link to /playground?view=consistency opens the tab when Consistency is enabled for your organization.
Send a packet by API
The API returns the same findings and evidence locations.
Background runs and page previews
Packets within 4 documents and 40 pages usually finish in the request. Larger packets run as background jobs for test and design-partner organizations. The tab shows progress and resumes checking after a page refresh. It shows the current page and time remaining when the engine reports them. Cancel stops checking in the browser. An accepted job may still finish on the server. Production organizations cannot send a packet that needs a background job yet.
Use synthetic documents only. The playground is a Preview surface.
Show side by side opens the finding's document and its matched document. Page regions appear only when the browser page shape matches the server's page shape. Text ranges appear on PDF pages only when the browser and server text hashes match. Otherwise, the view lists the location and explains why it cannot place the highlight. Images use page regions from the service's OCR. TIFF pages cannot be previewed. Details withheld for an outside-packet match have no displayed location. Opening a local preview does not upload the file again.