# CuRE Platform Documentation — full corpus > Every published CuRE documentation page, inline. Each section names the > canonical URL, the release it is pinned to, and the app it documents. --- # Notify sites about a safety finding URL: https://docs.principia.health/en/2026.07.1/canary/safety-notifications App: canary Release: 2026.07.1 Locale: en Raise a site safety notification from a SUSAR case or a validated signal, follow it from the bell, and acknowledge it once the safety team has acted. A safety notification records that the investigator sites must be told about a safety finding. Canary decides that a notification is required; Compend sends the safety letter to each site's investigator file and tracks each site's read receipt. Canary does not send the letter itself. ## Raise a notification You can notify the sites from two places: - **A SUSAR case.** Open the case on **Cases**. The **Site notification** section sits under the case's SUSAR reporting. - **A validated signal.** Open the signal on **Signals**. The **Site notification** section appears once the signal is validated. Select **Notify sites** and confirm. Canary records the requirement and hands it to Compend, which distributes the letter. A case or signal that has already been notified shows the date it was raised and whether it has been acknowledged, instead of offering a second notification. Notifications can also be raised for an expedited-reportable case (serious and causally related). These appear in the same list with the reason **Expedited- reportable case**. ## Follow open notifications The bell in the topbar lists the notifications still awaiting acknowledgement. Select **Open notifications** to go to the full list. The **Safety notifications** page shows every notification with its reason, the product and reaction it concerns, a link to the case or signal it came from, the date it was raised, and its state. Use **Show** to switch between **Awaiting acknowledgement**, **Acknowledged** and **All notifications**. ## Acknowledge a notification Once the safety team has acted on a notification, select **Acknowledge** on its row and confirm. The acknowledgement is recorded in the audited trail and cannot be undone. Acknowledging in Canary does not confirm that every site has read the letter. Each site's read receipt is tracked in Compend's safety distributions. ## When a list can't be read If Canary cannot read the notifications, the page and the case or signal section say so and offer **Retry**. An unreadable list is never shown as "nothing awaiting acknowledgement". --- # CuRE Capture URL: https://docs.principia.health/en/2026.07.1/capture/home App: capture Release: 2026.07.1 Locale: en AI-driven validation EDC for site coordinators. CuRE Capture is the platform's electronic data capture surface for CRCs and site coordinators — CRFs, AI-powered validation, a 21 CFR Part 11 audit trail, and query management. This page is scaffold content proving the versioned-docs pipeline. Per-app documentation authoring is a downstream content effort; the deep-link contract and publish pipeline are what this build stands up. ## Deep-linking here In-app help links to this page resolve to `/en/2026.07.1/capture/home` — the `{locale}/{version}/{app}/{contextKey}` quadruple produced by the `@cure-platform/support` deep-link builder for the Capture home context. --- # Query management URL: https://docs.principia.health/en/2026.07.1/capture/queries/overview App: capture Release: 2026.07.1 Locale: en Raising, routing, and resolving data queries in Capture. Query management is Capture's system of record for data queries. This page demonstrates a **nested** context key — it is served at `/en/2026.07.1/capture/queries/overview`, showing that a `contextKey` may span multiple path segments while remaining a single deep-link target. Scaffold content — the finished guide is authored downstream. --- # Draft and execute an agreement URL: https://docs.principia.health/en/2026.07.1/commons/agreements/lifecycle App: commons Release: 2026.07.1 Locale: en Draft a CDA, DUA, CTA, reliance agreement or MSA against an introduction, register its document, execute it with an electronic signature, and hand custody to Compend. Agreements records the deal paperwork for an introduction: confidential disclosure agreements (CDA), data use agreements (DUA), clinical trial agreements (CTA), central-IRB reliance agreements and master services agreements (MSA). An agreement moves from **Draft** to **Executed**, and an executed agreement can later be **Terminated**. Each agreement page shows this lifecycle as steps: drafted, document registered, executed, and custody in Compend. ## Draft an agreement 1. Open **Agreements** and, under the drafting form, choose the introduction the agreement belongs to, the agreement type and a title. 2. Select **Draft agreement**. The new agreement opens as a draft. If the introduction's site is anonymous, you can draft only after the site has accepted the introduction, because the agreement names both parties. ## Register the document Execution signs a specific document, identified by its SHA-256 digest. 1. On the draft, select **Register document**. 2. Choose the document file. Your browser computes its SHA-256 digest and only the digest is sent; Commons never receives or stores the document itself. If the browser can't fingerprint the file, or you computed the digest elsewhere, paste the 64-character SHA-256 instead. Until a document is registered, **Execute agreement** stays unavailable. Use **Replace document** if the text changes before signing; the new digest replaces the old one. ## Execute Select **Execute agreement** and complete the signature dialog. You re-enter your password, and the signature records its meaning (for example, "Executed the DUA") against the registered digest. After execution the agreement is **Executed**, the signature appears on the agreement page, and the executed copy is queued for Compend custody. Commons records your organization's signer of record only; the counterparty's own signature path is not part of Commons. ## Record custody Compend holds the executed document. When Compend assigns the executed copy its TMF artifact id, record it on the agreement with **Record custody** so the agreement points at its custody record. Until then the document state reads **Custody pending**. ## Terminate An executed agreement can be ended with **Terminate agreement** and a second signature ("Terminated the agreement"). Termination ends the agreement and can't be reversed. A terminated agreement that was never handed to Compend shows **No custody recorded**. ## Close the match with the agreement When you close the introduction on the brokering workbench, you can link the executed agreement to it; see **Broker a match into an introduction**. --- # Broker a match into an introduction URL: https://docs.principia.health/en/2026.07.1/commons/brokering/workbench App: commons Release: 2026.07.1 Locale: en Propose a match between your research interest and a site listing, review candidates, and carry an introduction through to a closed match. The brokering workbench is where a sponsor or CRO turns a research interest into a two-sided introduction with a site. Only demand-side organizations (sponsors and CROs) broker. A site sees why the workbench has no actions for it; it is matched by keeping its listings and capability metrics current. ## Propose a match 1. Under **Propose a match**, choose one of your research interests and a marketplace listing. 2. Review the **Match score**. A listing that fails a hard requirement of the interest is flagged; the score is an operational fit score, not a recommendation to enroll. 3. Select **Propose match**. The pair becomes a match candidate. You can propose against an anonymous listing. Its site stays hidden ("Site not disclosed yet") until the site accepts an introduction. You can also score listings against an interest from **Browse listings** and propose from there. The note under the form says whether a trained ranking model is available for your organization. Without one, candidates are ordered by the match score alone. ## Review match candidates The **Match candidates** list filters to **Open**, **Introduced**, **Declined** or **All**. A candidate is **New** when proposed and **In review** once someone starts reviewing it. From either state you can: - **Decline** it, which closes the candidate without contacting the site. - **Open introduction**, which asks the site to accept a two-sided introduction. Record any conflict of interest in the dialog so it travels with the introduction: **None declared**, or **Disclosed — needs broker review** with a disclosure note saying what was disclosed and by whom. ## Work an introduction An introduction starts **Awaiting site**. While it is open: - Record the site's answer with **Site accepted** or **Site declined**. - **Record COI** or **Review COI** to change the conflict-of-interest status. A disclosed conflict stays on the introduction until a broker review clears it. - **Withdraw** the introduction if the sponsor no longer wants to proceed. After the site accepts, its identity is revealed and you can draft the agreement for the introduction: **Draft one** opens Agreements. The agreement steps are in **Draft and execute an agreement**. ## Close the match Once the site has accepted, **Close introduction** records the match as done and can link the executed agreement for it. Closing is final: Commons tells Control the match is closed so the study can be set up there. If a conflict of interest is still disclosed and not cleared, the dialog says so before you confirm. Commons enforces the lifecycle on the server. If a change isn't allowed in the introduction's current state, the dialog or notification shows the reason and nothing changes. --- # CuRE Conduct URL: https://docs.principia.health/en/2026.07.1/conduct/home App: conduct Release: 2026.07.1 Locale: en Data integration, mapping, orchestration, and governance for data managers. CuRE Conduct is the platform's data-management surface — FHIR/HL7 → OMOP mapping, vocabulary management, data-quality rules, governance (consent scope, DUA), and provenance/lineage. This page is served at `/en/2026.07.1/conduct/home` and exists to prove the docs build handles multiple apps within one validated release. Content authoring is a downstream effort. --- # Verify a sealed dossier’s artifacts URL: https://docs.principia.health/en/2026.07.1/corridor/dossier-replay/overview App: corridor Release: 2026.07.1 Locale: en Compare supported template artifacts and replay qualified CEA runs against the evidence pinned in a sealed dossier. Corridor’s dossier replay view checks Calculate artifacts against the provenance and digest recorded in a sealed dossier version. The check is read-only: it does not change the seal, bound artifacts, or audit history. Calculate owns the methodology and computation; Corridor compares the returned evidence and shows the result. ## Run a check 1. Open **Model-run replay** in Corridor while signed in to the organization that owns the dossier. 2. Enter the **Dossier version seal id** for the version you want to check. 3. Select **Replay**. Review each artifact’s pinned methodology, version, input hash, digest, and comparison result before using the overall verdict. The supported scope includes CEA and BIA template artifact representations and qualified CEA runs with pinned, immutable inputs. A supported completed CEA run must belong to the same organization and match the methodology version and input hash recorded with the artifact. An arbitrary run identifier does not establish that a run is supported or qualified. Actual BIA runs remain unavailable pending their required validation-partner review. Unsupported methods, unknown runs, unqualified methods, missing pinned inputs, and an unavailable Calculate connection do not count as a match. ## Interpret the result - **MATCH** means the supported artifact representation or qualified CEA replay matches the pinned provenance and the sealed digest. - **MISMATCH** identifies a difference, such as a methodology version, input hash, or artifact digest. Inspect the named differences; the check does not replace the sealed artifact with the new result. - **UNAVAILABLE** means that artifact could not be checked within the supported scope. It is not evidence that the sealed result is correct. The overall **VERIFIED** verdict requires every pinned artifact to match. **DISCREPANCY** means at least one artifact differs. **INCOMPLETE** means at least one artifact is unavailable; investigate the reported reason and retry only when the missing prerequisite is restored. **NO_ARTIFACTS** means the sealed version contains no Calculate artifacts to check. A match is a reproducibility result within the supported method scope. It does not establish that assumptions are clinically appropriate, that a payer decision is warranted, or that an unqualified methodology has become validated. ## Sandbox and retained evidence Sandbox compares the static fixture representations used by sandbox binding. It does not execute a live Calculate model or demonstrate replay of a stored production run. The comparison honors the digest scheme recorded with each artifact. New raw-byte records compare the retained producer response representation; older records retain their canonical JSON comparison contract. Historical records without the needed evidence do not gain a successful result merely because another artifact can be checked.