# AI Transparency Alignment - Dermatology Image Annotation FHIR Implementation Guide v0.1.0

* [**Table of Contents**](toc.md)
* **AI Transparency Alignment**

## AI Transparency Alignment

### AI Transparency alignment

This IG implements the [HL7 AI Transparency on FHIR IG](https://build.fhir.org/ig/HL7/ai-transparency/) (ballot January 2026) to ensure that AI-generated dermatology annotations are identifiable, auditable, and distinguishable from human-produced results.

#### Primary mechanism: AIAST security tagging

The [AIPrediction](StructureDefinition-ai-prediction.md) profile requires `meta.security` to include the `AIAST` code from the `v3-ObservationValue` CodeSystem. This code, defined by the AI Transparency IG, signals that the resource contains content asserted by an artificial intelligence system.

Any resource that originates from or is informed by AI analysis carries the AIAST tag. This includes pure AI predictions and AI-assisted annotations where a clinician confirmed or corrected an AI result (see [ExampleAIAssistedConfirmed](Observation-ExampleAIAssistedConfirmed.md)).

#### Secondary mechanism: Provenance resources

For detailed audit trails, this IG uses Provenance resources to document which AI system produced a prediction, when it was created, and what source data it consumed. The [ExampleAIPredictionProvenance](Provenance-ExampleAIPredictionProvenance.md) demonstrates this pattern, recording the AI model Device as the agent and the source clinical photograph as the entity.

Provenance resources complement the AIAST tag by providing richer context that the security tag alone cannot convey: model identity, version, input data references, and temporal information.

#### Annotation method codes extend AIAST

The AIAST security tag answers a binary question: did AI participate in creating this content? Clinical workflows require more granularity. The [AnnotationMethod](CodeSystem-annotation-method.md) CodeSystem extends this concept with five levels of AI involvement:

* **expert-annotation** — specialist performed the full annotation without AI assistance
* **clinician-point-of-care** — treating clinician classified without AI assistance
* **ai-assisted-confirmed** — clinician reviewed an AI prediction and accepted it without modification
* **ai-assisted-corrected** — clinician reviewed an AI prediction and modified it before accepting
* **ai-inference** — AI model produced the prediction without human review

The AIAST tag alone cannot distinguish between a clinician who accepted an AI suggestion unchanged and one who corrected it before accepting. This distinction matters for clinical quality, training data curation, and AI performance monitoring. The annotation method codes fill that gap while maintaining compatibility with the AIAST tag for systems that only need the binary signal.

#### Practical implications

Systems that consume annotations from this IG can filter and sort by AI involvement at two levels of granularity. A simple filter on `meta.security = AIAST` identifies all AI-touched content. A more detailed query on `method` distinguishes clinician-confirmed from clinician-corrected results, enabling AI performance tracking and annotation quality analysis.

