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

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

Astacus Data Sender: Get Bundle for Patients

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

Astacus Data Sender: Get Bundle for aggregator

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

Behavior: Operation Definitions

These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.

Astacus Aggregator CQL

Evaluates a CQL expression and returns the results as a Parameters resource.

Astacus CQL

Evaluates a CQL expression and returns the results as a Parameters resource.

Behavior: Search Parameters

These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.

Search by _id in Patients with multipleOr

This SearchParameter enables query of patients by _id with mutlipleOr enabled.

Search by code:in in Conditions

This SearchParameter enables query of conditions by code with the in modifier.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Astacus Aggregator Bundle Profile

A collection of data for an Astacus patient.

Astacus Aggregator Parameters Profile

A parameters.

Astacus Cancer Patient Profile

A patient who has been diagnosed with or is receiving medical treatment for a malignant growth or tumor. The only difference between CancerPatient and FR Core Patient is that Patient.deceased is a must-support element in mCODE. Must-support is an instruction to implementers of FHIR clients and servers, rather than a constraint on data structure. Any Patient resource complying with US Core Patient Profile will also comply with CancerPatient.

Astacus Human Specimen Profile

A specimen taken from a Patient. The profile includes extensions to specify a more precise body site and an identifier of source body structure at that site (for example, a tumor identifier).

Astacus Laboratory Result Observation Profile

Astacus Laboratory Result Observation Profile is based upon the core FHIR Observation Resource, and, along with the Fr Core DiagnosticReport Profile for Laboratory Results Reporting. Laboratory results are grouped and summarized using the DiagnosticReport resource which reference Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) which references other observations, or rarely a laboratory test with component result values. The Fr Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases.

Astacus Patient Bundle Profile

A collection of data for an Astacus patient.

Astacus Patient Group Profile

A group of patients included in the scope of Astacus, whose cancer-related resources conform to identified profiles into this IG.

Astacus Procedure Profile

Astacus Procedure Profile is based upon the core FHIR Procedure Resource. This profile sets minimum expectations for the Procedure resource to record, search, and fetch procedures associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific uses cases.

French Primary Cancer Condition Profile

Records the the primary cancer condition, the original or first neoplasm in the body (Definition from: NCI Dictionary of Cancer Terms). Cancers that are not clearly secondary (i.e., of uncertain origin or behavior) should be documented as primary.

French Secondary Cancer Condition Profile

Records the history of secondary neoplasms, including location(s) and the date of onset of metastases. A secondary cancer results from the spread (metastasization) of cancer from its original site (Definition from: NCI Dictionary of Cancer Terms).

French Tumor Marker Test Profile

The result of a tumor marker test. Tumor marker tests are generally used to guide cancer treatment decisions and monitor treatment, as well as to predict the chance of recovery and cancer recurrence.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Astacus Procedure Codes

Concepts from CPT, SNOMED CT, HCPCS Level II Alphanumeric Codes, ICD-10-PCS,CDT and LOINC code systems that can be used to indicate the type of procedure performed.

Breast structure (body structure)

Value Set for Breast structure (body structure).

Malignant Neoplasm Breast Value Set

Value Set for Malignant Neoplasm Breast.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

astacus-1-endpoint
astacus-1-procedure-biopsy
astacus-1288992
astacus-179-malignant-neoplasm-breast
astacus-180-stain
astacus-181-antigen-ihc
astacus-182-antigen-fish
astacus-182-imaging
astacus-197-biopsy