Jev abstract screening protocol

Jev abstract screening protocol

An abstract can justify an exclusion or leave a question open. Apply the written review criteria without filling in methods the abstract never states.

abstract screening protocolLive API
Try an example

Population, topic and empirical design are explicit.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Apply the nonmedical protocol to the title and abstract.

Decision rules and labels
AdvanceExcludeUnclearReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

Screening applies the review protocol, not a general impression of whether a paper sounds useful. A relevant topic can still fail an explicit population or publication-type criterion.

Missing information is different from exclusion. An abstract that omits participant age has not established an adult population, but it has not proved the study used children either.

The source review plugin uses TypeSafe questions for title-and-abstract screening. These original software-education examples are a teaching adaptation, not medical advice or a claim that an automated literature review is complete.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Conceptual illustration of supplied evidence entering a typed decision contract.
Shared conceptual illustration of the input contract; not a screenshot or measured performance result.
How it works

Run abstract screening protocol in four steps.

Change the evidence, inspect the available labels, then compare the response with the rule.

  1. Illustration of adding the text or evidence for a decision

    Supply the evidence

    Use the named fields in the sample. Include the context that distinguishes the outcomes; leave absent facts explicitly unknown.

  2. Illustration of defining a question and its allowed choices

    Read the allowed outcomes

    The decision rule and the choice labels are sent with the evidence. Read the definitions before changing the labels. The model chooses among these supplied alternatives.

  3. Illustration of sending one input and comparing the returned choices

    Run and inspect the distribution

    The window makes a fresh server-side API request. It displays the highest-probability label, elapsed request time and estimated token cost. A provider failure produces an error, not a missing-evidence label.

  4. Illustration of reviewing a result and an uncertain item before using it

    Replay a pending local result

    Treat the returned label as a proposal. Check the evidence and distribution before consuming it in application code. Download the requests and saved observations. The offline consumer validates their hashes and prints a pending packet without executing it.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
All abstract criteriaAdvance96.0%
Opinion onlyExclude100%
Excluded populationExclude100%
Age group unknownUnclear100%
Protocol absentReview85.0%
Contradictory abstractReview98.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Worked example

Replay the exact requests

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Sample requests and authored expectations

Saved API observations

Single-request SDK runner

Offline preview consumer

Compare other decision examples

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Testing explicit inclusion and exclusion criteria on synthetic abstracts.
  • Separating absent methods information from a stated exclusion.
  • Preparing an uncertainty queue for a human full-text reviewer.

Outside this demonstration

  • Making final study-inclusion or evidence-quality decisions from a partial abstract alone.
  • Using these nonmedical examples as a clinical screening policy.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does Advance mean the study belongs in the final review?

No. It means the abstract meets the supplied criteria at this stage. A person still needs to check the full text and the actual protocol.

What happens to Unclear records?

They should remain available for follow-up under the review process. The label is not a reason to silently discard a record with missing abstract information.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.