Orthovision AI FHIR Implementation Guide
0.2.0 - ci-build

Orthovision AI FHIR Implementation Guide - Local Development build (v0.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Extension: Performer Device Extension

Official URL: http://medoco.health/fhir/StructureDefinition/performer-device Version: 0.2.0
Active as of 2025-10-29 Computable Name: PerformerDevice

Extension to reference a Device that performed the task. This extension addresses the gap in FHIR R4 and R5 specifications for tracking which specific AI system performed a task, providing forward compatibility with FHIR R6 native device performer support.

Context of Use

    This extension may be used on the following element(s)

Scope and Usage

The PerformerDevice extension addresses a critical gap in FHIR R4 and R5 specifications for tracking which specific AI system performed a task. While FHIR R6 introduces native support for devices as task performers, this extension provides backward compatibility and ensures consistent AI system identification across FHIR versions.

FHIR Version Compatibility

FHIR R4 and R5 Limitations: The current FHIR Task resource specification in R4 and R5 does not provide native support for identifying device performers. While Task.requestedPerformer can reference practitioners or organizations, it lacks the ability to precisely identify the specific device or AI system that actually performed the task.

FHIR R6 Evolution: FHIR R6 will introduce native support for device performers in Task resources, addressing this limitation directly in the specification. However, many implementations currently rely on R4 or R5 and need immediate solutions.

Technical Implementation

The extension accepts a Reference to a Device resource, specifically an OrthovisionAIModel in this implementation guide. The referenced device should contain comprehensive information about the AI system including:

  • Manufacturer: The organization that developed the AI system
  • Device Name: The specific AI model or system name
  • Model Number: Version identifier for the AI system
  • Software Version: Specific version of the AI software
  • Configuration: Any relevant configuration parameters that might affect results

Usage Patterns

During Task Creation: When a task is submitted for AI processing, the performerDevice extension is typically empty, as the specific AI system that will process the task may not yet be determined.

During Task Execution: As the AI system begins processing, the server populates the performerDevice extension with a reference to the specific AI model being used.

Upon Task Completion: The completed task maintains the performerDevice reference, providing a permanent record of which AI system generated the classification results.

Migration Path to FHIR R6

When FHIR R6 becomes available and implementations upgrade, the information captured in this extension can be migrated to the native R6 device performer fields.

Usage info

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Extension Content

Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.

This structure is derived from Extension

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension Performer Device Extension
... extension 0..0 Extension
... url 1..1 uri "http://medoco.health/fhir/StructureDefinition/performer-device"
... value[x] 0..1 Reference(Device) Value of extension

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension Performer Device Extension
... id 0..1 id Unique id for inter-element referencing
... extension 0..0 Extension
Slice: Unordered, Open by value:url
... url 1..1 uri "http://medoco.health/fhir/StructureDefinition/performer-device"

doco Documentation for this format

This structure is derived from Extension

Summary

Simple Extension with the type Reference: Extension to reference a Device that performed the task. This extension addresses the gap in FHIR R4 and R5 specifications for tracking which specific AI system performed a task, providing forward compatibility with FHIR R6 native device performer support.

Differential View

This structure is derived from Extension

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension Performer Device Extension
... extension 0..0 Extension
... url 1..1 uri "http://medoco.health/fhir/StructureDefinition/performer-device"
... value[x] 0..1 Reference(Device) Value of extension

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension Performer Device Extension
... id 0..1 id Unique id for inter-element referencing
... extension 0..0 Extension
Slice: Unordered, Open by value:url
... url 1..1 uri "http://medoco.health/fhir/StructureDefinition/performer-device"

doco Documentation for this format

This structure is derived from Extension

Summary

Simple Extension with the type Reference: Extension to reference a Device that performed the task. This extension addresses the gap in FHIR R4 and R5 specifications for tracking which specific AI system performed a task, providing forward compatibility with FHIR R6 native device performer support.

 

Other representations of profile: CSV, Excel, Schematron

Constraints

Id Grade Path(s) Description Expression
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()