{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T00:44:04.075Z",
  "record_id": "VXI-EXT-ADMINISTRATION-FHIR-DOCUMENT-REFERENCE-PROVENANCE-SEPARATION-01-v1",
  "record_kind": "external_reference",
  "title": "FHIR R5 reference and document provenance",
  "system": "HL7 FHIR R5 5.0.0 — documentreference",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does provenance of a FHIR DocumentReference establish who created the underlying document?",
  "near_questions": [
    "Does DocumentReference provenance identify the document author?",
    "Can another actor index a document later?",
    "Why are two provenance histories needed for a document reference?",
    "What distinguishes document creation from metadata registration?"
  ],
  "supported_claims": [
    {
      "claim": "R5 describes two provenance histories: the underlying document and the DocumentReference that points to it. Another actor may create the reference later, and its metadata describes that reference history. Preserve the document origin separately rather than attributing authorship of the content to whoever created its reference.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "No clinical advice, patient-safety validation, legal compliance or confirmation of insurance cover.",
    "No independent proof of a live access decision, completed workflow, physical action or settled payment.",
    "The published R5 definition does not establish support or conformance in a buyer implementation.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "R5 describes two provenance histories: the underlying document and the DocumentReference that points to it. Another actor may create the reference later, and its metadata describes that reference history. Preserve the document origin separately rather than attributing authorship of the content to whoever created its reference.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "HL7 FHIR R5 5.0.0 — documentreference",
    "source_url": "https://hl7.org/fhir/R5/documentreference.html",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-ADMINISTRATION-FHIR-DOCUMENT-REFERENCE-PROVENANCE-SEPARATION-01-v1",
    "candidate_record_sha256": "f0e9e9c66337b63a48a8697e05162d4232fbd34065db5929ae2405bae34b7e98",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "R5 describes two provenance histories: the underlying document and the DocumentReference that points to it. Another actor may create the reference later, and its metadata describes that reference history. Preserve the document origin separately rather than attributing authorship of the content to whoever created its reference.",
    "required_buyer_context": "Document provenance; Reference provenance; Document and reference version bindings. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-25",
    "claim_to_check": "Does provenance of a FHIR DocumentReference establish who created the underlying document?",
    "documented_statement": {
      "status": "documented",
      "statement": "R5 describes two provenance histories: the underlying document and the DocumentReference that points to it. Another actor may create the reference later, and its metadata describes that reference history. Preserve the document origin separately rather than attributing authorship of the content to whoever created its reference.",
      "source_ids": [
        "fhir-documentreference"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Avoid confusing an indexing actor with the document creator. This is a documentation-review judgment, not an observed outcome.",
      "source_ids": [
        "fhir-documentreference"
      ]
    },
    "buyer_evidence_required": [
      "Document provenance",
      "Reference provenance",
      "Document and reference version bindings"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse content-authorship attribution from reference provenance alone."
    },
    "unknowns": "The applicable implementation guide, live system and actual administrative outcome were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The applicable implementation guide, live system and actual administrative outcome were not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "fhir-documentreference",
        "url": "https://hl7.org/fhir/R5/documentreference.html",
        "final_url": "https://hl7.org/fhir/R5/documentreference.html",
        "status": 200,
        "captured_at_utc": "2026-10-25T00:21:10.758Z",
        "sha256": "74838901c37120a5b68ca8dcd634be1873515c1690870a5338e608198fb0599c",
        "bytes": 401108,
        "title": "HL7 FHIR R5 5.0.0 — documentreference",
        "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
        "rights_review": "Original factual paraphrase of the HL7 FHIR core specification under CC0. Third-party terminology and trademarks have separate terms; no document, schema, code or modified standard is redistributed. No endorsement or patient data.",
        "checked_on": "2026-10-25",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "10.2.2 Boundaries and Relationships"
        ],
        "version_context": "Permanent FHIR R5 5.0.0 publication. Resource-specific maturity and normative/Trial Use status apply; no universal normative or implementation-conformance claim."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Avoid confusing an indexing actor with the document creator.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the applicable FHIR version, implementation guide, resource profile and independent administrative outcome before relying on a current workflow."
    },
    "buyer_relevance": "Avoid confusing an indexing actor with the document creator.",
    "refusal_conditions": [
      "Refuse content-authorship attribution from reference provenance alone."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Avoid confusing an indexing actor with the document creator.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#fhir-document-reference-provenance-separation",
  "machine_readable_record": "/varexis-index/records/fhir-document-reference-provenance-separation.json"
}