{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "pub-8-tranche-58-v1",
  "route_id": "agentic_reviewed_fhir_batch_interdependent_create_boundary",
  "record_id": "VXI-EXT-ADMINISTRATION-FHIR-BATCH-INTERDEPENDENT-CREATE-BOUNDARY-01-v1",
  "question": "Can a FHIR batch create one resource and rely on another entry referencing that new resource?",
  "answer": "FHIR R5 requires batch changes to be independent. References from one batch entry to a resource being created by another are non-conformant. Linked changes need the appropriate transaction and server-support contract; merely putting them in one HTTP request does not establish atomic execution.",
  "records": [
    {
      "record_id": "VXI-EXT-ADMINISTRATION-FHIR-BATCH-INTERDEPENDENT-CREATE-BOUNDARY-01-v1",
      "url": "/varexis-index/records/fhir-batch-interdependent-create-boundary.json",
      "content_sha256": "d9fe72f037cf0854cb3a7af96ccb4aeaea9f7d6985ee93aefd9d9d235463af90",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-25T00:44:04.075Z",
        "record_id": "VXI-EXT-ADMINISTRATION-FHIR-BATCH-INTERDEPENDENT-CREATE-BOUNDARY-01-v1",
        "record_kind": "external_reference",
        "title": "FHIR R5 dependent changes need transaction semantics",
        "system": "HL7 FHIR R5 5.0.0 — http",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Can a FHIR batch create one resource and rely on another entry referencing that new resource?",
        "near_questions": [
          "Can one FHIR batch entry reference another newly created entry?",
          "Are dependencies allowed between batch changes?",
          "Does one HTTP request make FHIR changes atomic?",
          "What must be checked for linked administrative updates?"
        ],
        "supported_claims": [
          {
            "claim": "FHIR R5 requires batch changes to be independent. References from one batch entry to a resource being created by another are non-conformant. Linked changes need the appropriate transaction and server-support contract; merely putting them in one HTTP request does not establish atomic execution.",
            "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": "FHIR R5 requires batch changes to be independent. References from one batch entry to a resource being created by another are non-conformant. Linked changes need the appropriate transaction and server-support contract; merely putting them in one HTTP request does not establish atomic execution.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "HL7 FHIR R5 5.0.0 — http",
          "source_url": "https://hl7.org/fhir/R5/http.html",
          "checked_on": "2026-10-25",
          "candidate_record_id": "VXI-EXT-ADMINISTRATION-FHIR-BATCH-INTERDEPENDENT-CREATE-BOUNDARY-01-v1",
          "candidate_record_sha256": "a4b915742718f89217407eb93138bc2c5fe94892f15405cfb79b53edbdedc4b5",
          "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": "FHIR R5 requires batch changes to be independent. References from one batch entry to a resource being created by another are non-conformant. Linked changes need the appropriate transaction and server-support contract; merely putting them in one HTTP request does not establish atomic execution.",
          "required_buyer_context": "Referenced resources and identities; Batch or transaction type; Server support and individual results. 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 batch create one resource and rely on another entry referencing that new resource?",
          "documented_statement": {
            "status": "documented",
            "statement": "FHIR R5 requires batch changes to be independent. References from one batch entry to a resource being created by another are non-conformant. Linked changes need the appropriate transaction and server-support contract; merely putting them in one HTTP request does not establish atomic execution.",
            "source_ids": [
              "fhir-http"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Avoid relying on unsupported dependencies between batched changes. This is a documentation-review judgment, not an observed outcome.",
            "source_ids": [
              "fhir-http"
            ]
          },
          "buyer_evidence_required": [
            "Referenced resources and identities",
            "Batch or transaction type",
            "Server support and individual results"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Refuse atomic linked-change claims from a batch envelope."
          },
          "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-http",
              "url": "https://hl7.org/fhir/R5/http.html",
              "final_url": "https://hl7.org/fhir/R5/http.html",
              "status": 200,
              "captured_at_utc": "2026-10-25T00:21:11.131Z",
              "sha256": "fcf508c5e0b7cb704d7f2c394d3addfaaad88fb0ee45e153fd8dcdc0c2a61d41",
              "bytes": 204605,
              "title": "HL7 FHIR R5 5.0.0 — http",
              "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": [
                "3.2.0.11; 3.2.0.11.1 Batch",
                "3.2.0.11.1 Batch"
              ],
              "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 relying on unsupported dependencies between batched changes.",
            "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 relying on unsupported dependencies between batched changes.",
          "refusal_conditions": [
            "Refuse atomic linked-change claims from a batch envelope."
          ]
        },
        "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 relying on unsupported dependencies between batched changes.",
          "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-batch-interdependent-create-boundary",
        "machine_readable_record": "/varexis-index/records/fhir-batch-interdependent-create-boundary.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": "3f68e6dc816db5071cff8c9cc385499fc44b4f6205a3ca4f63d211068e74eae5"
}