{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "pub-8-tranche-58-v1",
  "route_id": "agentic_reviewed_fhir_document_append_context",
  "record_id": "VXI-EXT-ADMINISTRATION-FHIR-DOCUMENT-APPEND-CONTEXT-01-v1",
  "question": "Can a FHIR document that appends another document be reviewed as a complete standalone record?",
  "answer": "R5 DocumentReference identifies relationships between documents. Where a document appends another, the definition says it cannot be fully understood without the referenced target. A standalone export of the appended material may therefore omit required context even when its own file is complete.",
  "records": [
    {
      "record_id": "VXI-EXT-ADMINISTRATION-FHIR-DOCUMENT-APPEND-CONTEXT-01-v1",
      "url": "/varexis-index/records/fhir-document-append-context.json",
      "content_sha256": "8f354e207c6d3dbfe751454e01de8bdfd225a739feaeb086ca8ac633fd7a771d",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-25T00:44:04.075Z",
        "record_id": "VXI-EXT-ADMINISTRATION-FHIR-DOCUMENT-APPEND-CONTEXT-01-v1",
        "record_kind": "external_reference",
        "title": "FHIR R5 append document completeness",
        "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": "Can a FHIR document that appends another document be reviewed as a complete standalone record?",
        "near_questions": [
          "Can a FHIR appended document stand alone?",
          "What context is needed for an append relationship?",
          "Can a complete file still be an incomplete document record?",
          "Which linked document must accompany an appended export?"
        ],
        "supported_claims": [
          {
            "claim": "R5 DocumentReference identifies relationships between documents. Where a document appends another, the definition says it cannot be fully understood without the referenced target. A standalone export of the appended material may therefore omit required context even when its own file is complete.",
            "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 DocumentReference identifies relationships between documents. Where a document appends another, the definition says it cannot be fully understood without the referenced target. A standalone export of the appended material may therefore omit required context even when its own file is complete.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "HL7 FHIR R5 5.0.0 — documentreference definitions",
          "source_url": "https://hl7.org/fhir/R5/documentreference-definitions.html",
          "checked_on": "2026-10-25",
          "candidate_record_id": "VXI-EXT-ADMINISTRATION-FHIR-DOCUMENT-APPEND-CONTEXT-01-v1",
          "candidate_record_sha256": "674887f02aba00564b538bc967ba88eed8d60304b582626c75de8d426907ecde",
          "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 DocumentReference identifies relationships between documents. Where a document appends another, the definition says it cannot be fully understood without the referenced target. A standalone export of the appended material may therefore omit required context even when its own file is complete.",
          "required_buyer_context": "Relationship code; Referenced target document; Appended content and versions. 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": "Can a FHIR document that appends another document be reviewed as a complete standalone record?",
          "documented_statement": {
            "status": "documented",
            "statement": "R5 DocumentReference identifies relationships between documents. Where a document appends another, the definition says it cannot be fully understood without the referenced target. A standalone export of the appended material may therefore omit required context even when its own file is complete.",
            "source_ids": [
              "fhir-documentreference-definitions"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Retain the related document needed to interpret an append. This is a documentation-review judgment, not an observed outcome.",
            "source_ids": [
              "fhir-documentreference-definitions"
            ]
          },
          "buyer_evidence_required": [
            "Relationship code",
            "Referenced target document",
            "Appended content and versions"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Refuse complete-context claims from an append without its target."
          },
          "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-definitions",
              "url": "https://hl7.org/fhir/R5/documentreference-definitions.html",
              "final_url": "https://hl7.org/fhir/R5/documentreference-definitions.html",
              "status": 200,
              "captured_at_utc": "2026-10-25T00:21:10.747Z",
              "sha256": "3df1187574a0ccfb8f7805ee59877ca76c0af487629eb6e47642302908f9881f",
              "bytes": 51412,
              "title": "HL7 FHIR R5 5.0.0 — documentreference definitions",
              "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": [
                "DocumentReference.status; DocumentReference.docStatus",
                "DocumentReference.relatesTo.code",
                "DocumentReference.securityLabel"
              ],
              "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": "Retain the related document needed to interpret an append.",
            "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": "Retain the related document needed to interpret an append.",
          "refusal_conditions": [
            "Refuse complete-context claims from an append without its target."
          ]
        },
        "niche": {
          "niche_id": "enterprise-ai-data-custody-exit-assurance",
          "label": "Enterprise AI Data Custody & Exit Assurance",
          "classification_id": "custody",
          "classification_label": "AI Data Custody, Retention & Exit Assurance",
          "topic_id": "custody",
          "buyer_intent": "Retain the related document needed to interpret an append.",
          "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-append-context",
        "machine_readable_record": "/varexis-index/records/fhir-document-append-context.json"
      }
    }
  ],
  "access": {
    "mode": "exact_http_only",
    "payment_required": false,
    "purchase_url": null,
    "mcp_preview_available": false,
    "paid_saved_retrieval_available": false,
    "natural_language_search_qualified": false
  },
  "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.",
  "content_sha256": "67c20b546911136256993d168aa0d09063620f7e34c4864c9ff398af782238b2"
}
