> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/guides/data-to-verified-action.md).

# Data to a Verified Action

Follow a synthetic record from a supported source through queryable data and agent access to an independently verified external integration outcome.

Use a synthetic record and an approved test destination to verify the whole data path. Obtain a configured source, supported mapping, permitted read access, and an integration whose test behavior and mutation permissions are understood. If any prerequisite is missing, complete provisioning before running the corresponding step.

For a hospital integration, first agree on the [exchange pattern and interface scope](https://docs.concurrence.com/data/healthcare-interoperability). Inbound patient or scheduling notifications and outbound changes need separate access, tests, and confirmation. The steps below assume a supported, provisioned source and target.

<figure><img src="https://1651797362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2YwM0LHtEGLt9S21OyC3%2Fuploads%2Fgit-blob-1b8b808583aadcf0517cf69a0f66538d6dea14f9%2Fdata-verification-flow.svg?alt=media" alt="Follow a synthetic record through input acceptance, asynchronous queryability, demonstrated agent retrieval, path-specific authorization, and independent confirmation in the target system."><figcaption><p>Each arrow requires new evidence. Acceptance does not establish queryability, retrieval, or external completion.</p></figcaption></figure>

## Define the Data and Action Contract

Choose one bounded workflow and record what makes its inputs usable. For clinical measurements, use [Reusable Clinical Data](https://docs.concurrence.com/data/clinical-data-contracts) to specify subject identity, units, measurement time, allowed age, missing-data behavior, and calculation version. Keep the original source references with the normalized result.

Name the system that owns the task and the system that confirms the action. They can be different: an application can own a referral task while the scheduling system owns its booking. Define the evidence that permits each step to complete, the response to a concurrent change, and the owner of an ambiguous result.

Prepare synthetic cases with known expected results. For the BMI mapping example, 70 kg with 175 cm and 70,000 g with 1.75 m both produce 22.86 kg/m² for display. A missing weight unit or zero height takes the specified rejection or review path. These cases validate a calculation, not clinical eligibility.

## Connect the Source

Configure a supported [intake source](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/intake-sources.md) or submit records through [FHIR import](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/fhir.md). Data-source records are not polled. Record the source identifier and the submitted record's external identifier so that you can locate the same record later.

[Authenticated dataset intake](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/intake.md) and [browser Surfaces](https://docs.concurrence.com/developer-guide/platform-api/conversations/surfaces.md) have different contracts. A Surface submission does not automatically create a dataset file. Source support and parsing must be confirmed for the chosen format.

## Verify Queryable Data

Use **Data → Records** and the relevant [entity read](https://docs.concurrence.com/developer-guide/platform-api/data-world-model.md#entity-reads) or [FHIR resource read](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/fhir.md) to locate the intended record and inspect source attribution. Verify its identity and the fields needed by the workflow. World-model read views update asynchronously; acceptance of an input is not evidence that the corresponding projection is already queryable.

If the record is missing or stale, inspect source status, mapping, identity resolution, and freshness before resubmitting. Preserve the original identifiers. Caller recognition may require a separate [external identity binding](https://docs.concurrence.com/developer-guide/platform-api/integrations/external-user-subject-key-binding.md); a queryable record alone does not prove recognition is ready.

Compare the read result with the prepared case: subject, source values, normalized units, measurement time, and calculation inputs. Check the source's clinical time separately from receipt time; a fresh import can contain an old measurement. For a derived value, retain its input references and calculation version in the test evidence. Use [pipeline monitoring](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/connector-runner.md) for stored ingestion evidence, then verify the specific record through its supported read interface.

## Verify Agent Access

Configure the test service with the intended graph, query/tool access, and subject context. Run the bounded interaction from [First Verified Conversation](https://docs.concurrence.com/developer-guide/guides/first-verified-conversation.md) against that configured test service. Check the retained answer and available tool evidence against the synthetic source record. A plausible answer does not establish that the agent retrieved the intended source.

Expose the reviewed calculation through a supported [platform function](https://docs.concurrence.com/developer-guide/platform-api/functions.md) or [workspace data query](https://docs.concurrence.com/developer-guide/platform-api/functions/workspace-data-queries.md) as appropriate to its inputs. Workspace queries read workspace-owned tables; they are not an automatic query path into every world-model view. Verify the returned value, missing-data behavior, and permitted subject selection before testing the conversation.

## Verify the External Outcome

Follow [Verify an Integration Action](https://docs.concurrence.com/developer-guide/guides/verify-an-integration-action.md) for the authorized test mutation, expected failure, target acknowledgement or read-back, and reconciliation. Apply approval requirements only to the integration path that implements them.

| Milestone                 | Evidence to keep                                                             |
| ------------------------- | ---------------------------------------------------------------------------- |
| Submitted                 | Source and request identifiers, and input acceptance or rejection            |
| Queryable                 | Intended entity, source attribution, required fields, and observed freshness |
| Used by the workflow      | Service/version, conversation/run, and available retrieval or tool evidence  |
| Authorized                | Required permission and approval decision for the specific action            |
| Completed externally      | Target acknowledgement or independent read-back                              |
| Reconciled and cleaned up | Resolution of ambiguous attempts and cleanup of the permitted test resources |

Stop at the last verified milestone when later evidence is missing. Use [Troubleshooting](https://docs.concurrence.com/developer-guide/guides/troubleshooting.md) for the next diagnostic rather than repeating an uncertain mutation.

## Exercise Corrections and Concurrent Changes

Run the cases below against the selected integration and application contracts. Record the actual outcome and owner when a required behavior is unavailable. Do not treat an authored instruction as enforcement.

| Case                                           | Evidence of the intended behavior                                                                                          |
| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Repeat the same source record                  | The chosen ingestion or application deduplication policy preserves one logical observation for the calculation             |
| Deliver a measurement after its clinical date  | The calculation applies the agreed time window, and receipt time does not silently replace measurement time                |
| Correct an input already used by a task        | The new derivation is inspectable and the task owner rechecks affected pending work                                        |
| Submit two competing task updates              | The authoritative application detects or serializes the conflict under its documented mutation contract                    |
| Change the user's request during a slow lookup | The application checks that the returned result still belongs to the active request                                        |
| Lose the response after an external write      | The action stays unresolved until destination evidence is reconciled. Retries follow that operation's idempotency contract |

In a version-checked application, capture both the version each client read and the version accepted by the mutation. Keep any rejected edit available for review or reapplication. An optimistic display of an edit is not confirmation that the shared projection or external system accepted it.

## Finish with a Reusable Evidence Package

Keep the synthetic source records, mapping and calculation versions, expected and observed outputs, service configuration, run references, destination confirmation, and recovery results together. Have the implementation owner identify unresolved cases and the evidence required to close them.

End test conversations and cancel synthetic bookings or tasks through the system that owns them. Handle retained test records under the workspace's retention policy. Ending a conversation does not erase its evidence.

Production use adds authorized source access, clinical acceptance, representative data coverage, channel provisioning, workload testing, and operating support. Before using the same logic for a second workflow, review its [reuse package and deployment bindings](https://docs.concurrence.com/data/connect-another-workflow#package-the-reusable-parts).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/guides/data-to-verified-action.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
