Implementation Guide for Astacus project
0.0.1 - ci-build France flag

Implementation Guide for Astacus project - Local Development build (v0.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CapabilityStatement: Astacus Data Sender: Get Bundle for aggregator (Experimental)

Official URL: https://aphp.fr/fhir/fr/astacus/CapabilityStatement/astacus-sender-aggregator-cql-bundle Version: 0.0.1
Draft as of 2023-04-11 Computable Name: CapabilityStatementAggregatorCQLBundle

Retrieves a Bundle of references to length of Patient that conform to Astacus.

Raw OpenAPI-Swagger Definition file | Download

Astacus Data Sender: Get Bundle for aggregator

  • Implementation Guide Version: 0.0.1
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats:
  • Published on: 2023-04-11 14:00:00+0200
  • Published by: APHP

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as "SHALL NOT". A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

SHALL Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

An Astacus Server SHALL:

  1. Support all profiles defined in this Implementation Guide..
  2. Implement the RESTful behavior according to the FHIR specification.
  3. Return the following response classes:
    • (Status 400): invalid parameter
    • (Status 401/4xx): unauthorized request
    • (Status 403): insufficient scope
    • (Status 404): unknown resource
    • (Status 410): deleted resource.
  4. Support json source formats for all Astacus interactions.
  5. Identify the Astacus profiles supported as part of the FHIR meta.profile attribute for each instance.
  6. Support the searchParameters on each profile individually and in combination.

The Astacus Server SHOULD:

  1. Support xml source formats for all Astacus interactions.
Security
  1. See the General Security Considerations section for requirements and recommendations.
  2. A server SHALL reject any unauthorized requests by returning an HTTP 401 unauthorized response code.
Summary of System-wide Interactions