Developer guidesIntegrationData & trustHelp

Developer guides · Updated September 14, 2026

Follow a record from source to publication

Three fictional entries show the same workflow at approved, revision and pending stages. Filter them, inspect their provenance and download the fixture.

Illustrative workflow fixture, not a production API response or licensed dataset. All records, sources and reviewer identities are fictional. No clinical facts, patient records or medical recommendations are included.

EXAMPLE-001

Reference catalog entry A

approved

Source

Fictional reference record A — created for this example

Synthetic metadata authored for the MedicalLibrary public evaluation sample

Review

Metadata fields checked for this fictional example

Example reviewer

Publication

published
Version 1

Inspect the JSON record
{
  "id": "EXAMPLE-001",
  "title": "Reference catalog entry A",
  "source": {
    "id": "SOURCE-A",
    "citation": "Fictional reference record A — created for this example",
    "provenance": "Synthetic metadata authored for the MedicalLibrary public evaluation sample"
  },
  "review": {
    "status": "approved",
    "decision": "Metadata fields checked for this fictional example",
    "reviewer": "Example reviewer"
  },
  "publication": {
    "status": "published",
    "version": 1
  },
  "content": {
    "summary": "A fictional catalog record demonstrating a source, a review decision and a published version."
  }
}

EXAMPLE-002

Reference catalog entry B

needs revision

Source

Fictional reference record B — created for this example

Synthetic metadata authored for the MedicalLibrary public evaluation sample

Review

A source locator would need clarification before approval

Example reviewer

Publication

not published
No published version

Inspect the JSON record
{
  "id": "EXAMPLE-002",
  "title": "Reference catalog entry B",
  "source": {
    "id": "SOURCE-B",
    "citation": "Fictional reference record B — created for this example",
    "provenance": "Synthetic metadata authored for the MedicalLibrary public evaluation sample"
  },
  "review": {
    "status": "needs_revision",
    "decision": "A source locator would need clarification before approval",
    "reviewer": "Example reviewer"
  },
  "publication": {
    "status": "not_published",
    "version": null
  },
  "content": {
    "summary": "A fictional record illustrating a review that has not reached publication."
  }
}

EXAMPLE-003

Reference catalog entry C

pending

Source

Fictional reference record C — created for this example

Synthetic metadata authored for the MedicalLibrary public evaluation sample

Review

No decision recorded.

No reviewer assigned.

Publication

not published
No published version

Inspect the JSON record
{
  "id": "EXAMPLE-003",
  "title": "Reference catalog entry C",
  "source": {
    "id": "SOURCE-C",
    "citation": "Fictional reference record C — created for this example",
    "provenance": "Synthetic metadata authored for the MedicalLibrary public evaluation sample"
  },
  "review": {
    "status": "pending",
    "decision": null,
    "reviewer": null
  },
  "publication": {
    "status": "not_published",
    "version": null
  },
  "content": {
    "summary": "A fictional record illustrating work that still awaits a reviewer decision."
  }
}

Make a first request to the fixture

On this sample page, run this JavaScript in your browser’s developer console. It reads the public JSON file and prints EXAMPLE-001. No account or API key is required.

const sample = await fetch("../assets/evaluation-sample.json")
  .then(response => {
    if (!response.ok) throw new Error(response.status);
    return response.json();
  });
const published = sample.entries.filter(
  entry => entry.publication.status === "published"
);
console.log(published[0].id); // EXAMPLE-001

This requests a static sample file from the website. It does not call the production MedicalLibrary API.

What the fields mean

  • source records the origin and citation for this fictional entry.
  • review records the example decision separately from the content.
  • publication distinguishes approved work from a published version.
  • content contains a nonclinical explanation of the example.

Use the fixture to discuss your requirements. Ask for the actual content contract, rights and coverage before integrating real data.

Keep moving

For an existing evaluation, email support@medicallibrarytech.com. Do not include credentials, patient information or confidential records.