Synthetic validation
Executable checks keep SCRIMED synthetic workflows honest before live integrations.
Each scenario is evaluated for synthetic-only labeling, identifier safety, contract boundaries, risk markers, workflow trace completeness, assertions, and human review guardrails.
pass
care-navigation-high-risk-followup
12 passed, 0 failed
Review fixture and assertionspass
docutwin-note-review
12 passed, 0 failed
Review fixture and assertionspass
trialcore-eligibility-screen
12 passed, 0 failed
Review fixture and assertionsSynthetic-only label
Scenario content must clearly identify itself as synthetic.
No production identifiers
Scenario content must not include obvious SSN, MRN, email, or phone identifiers.
Fixture payload present
Scenario must have a structured request and expected-output fixture.
Fixture identifier safety
Fixture payload must not include obvious SSN, MRN, email, or phone identifiers.
Fixture synthetic-only flag
Fixture request must be explicitly marked synthetic-only.
Contract boundary
Synthetic validation scenarios must stay bound to the synthetic clinical test contract.
Risk markers retained
Scenario must retain at least three explicit risk markers.
Workflow trace complete
Scenario must expose at least four deterministic workflow trace steps.
Fixture trace alignment
Fixture expected trace must align with the scenario workflow trace.
Assertions mapped
Scenario must include at least four explicit assertions.
Fixture output contract
Fixture must define expected output signals and prohibited claims.
Human review guardrail
Scenario must retain a review, draft, no-final-claim, or Watchtower guardrail.
Synthetic-only label
Scenario content must clearly identify itself as synthetic.
No production identifiers
Scenario content must not include obvious SSN, MRN, email, or phone identifiers.
Fixture payload present
Scenario must have a structured request and expected-output fixture.
Fixture identifier safety
Fixture payload must not include obvious SSN, MRN, email, or phone identifiers.
Fixture synthetic-only flag
Fixture request must be explicitly marked synthetic-only.
Contract boundary
Synthetic validation scenarios must stay bound to the synthetic clinical test contract.
Risk markers retained
Scenario must retain at least three explicit risk markers.
Workflow trace complete
Scenario must expose at least four deterministic workflow trace steps.
Fixture trace alignment
Fixture expected trace must align with the scenario workflow trace.
Assertions mapped
Scenario must include at least four explicit assertions.
Fixture output contract
Fixture must define expected output signals and prohibited claims.
Human review guardrail
Scenario must retain a review, draft, no-final-claim, or Watchtower guardrail.
Synthetic-only label
Scenario content must clearly identify itself as synthetic.
No production identifiers
Scenario content must not include obvious SSN, MRN, email, or phone identifiers.
Fixture payload present
Scenario must have a structured request and expected-output fixture.
Fixture identifier safety
Fixture payload must not include obvious SSN, MRN, email, or phone identifiers.
Fixture synthetic-only flag
Fixture request must be explicitly marked synthetic-only.
Contract boundary
Synthetic validation scenarios must stay bound to the synthetic clinical test contract.
Risk markers retained
Scenario must retain at least three explicit risk markers.
Workflow trace complete
Scenario must expose at least four deterministic workflow trace steps.
Fixture trace alignment
Fixture expected trace must align with the scenario workflow trace.
Assertions mapped
Scenario must include at least four explicit assertions.
Fixture output contract
Fixture must define expected output signals and prohibited claims.
Human review guardrail
Scenario must retain a review, draft, no-final-claim, or Watchtower guardrail.