Skip to content

Device Profile

Canonical../StructureDefinition/nexus-emr-core-emrdevice
Statusdraft · 1.26.0
BaseDevice (constraint)
SourceFSH · JSON

Represents an EMR software application/product, capturing key details like manufacturer, product name/model, type, version, and the owning organization using standard Nexus EMR references. Uses a non-instance-specific identifier for the Device itself.

Overview

Overview

The Nexus EMR Core EmrDevice profile represents Electronic Medical Record (EMR) software systems within the Nexus EMR ecosystem. Based on the FHIR Device resource, this profile captures essential metadata about EMR applications including vendor, product name, version, and ownership information for integration and data provenance tracking.

Key Features

  • Vendor Identification: Tracks EMR manufacturer/vendor information
  • Product Documentation: Captures commercial product names and models
  • Version Management: Records software version for compatibility tracking
  • Ownership Attribution: Links EMR to operating organization
  • Software Classification: Explicitly identifies devices as software systems

Purpose and Use Cases

The EmrDevice profile supports:

  • Data Provenance: Tracking which EMR system generated clinical data
  • Integration Management: Understanding source system capabilities
  • Compatibility Checking: Version-based feature availability
  • Audit Trails: Documenting data sources and transformations
  • Multi-vendor Environments: Managing heterogeneous EMR landscapes

EMR Metadata Components

Essential elements include:

  • Manufacturer: Vendor company name (Epic, Cerner, etc.)
  • Device Name: Commercial product name or model
  • Type: Fixed as "software" to distinguish from hardware
  • Version: Software version string for compatibility
  • Owner: Healthcare organization operating the EMR

Integration Scenarios

The profile enables:

  • Source system identification in data exchanges
  • EMR capability discovery
  • Version-specific data mapping
  • Vendor-specific integration logic
  • Multi-tenant environment management

Data Quality and Governance

Supports tracking of:

  • Data lineage from source EMRs
  • Version-specific data quality issues
  • Vendor-specific data patterns
  • Integration points and interfaces
  • Compliance with EMR standards

Relationships

EmrDevice connects to:

  • Organization: The healthcare entity operating the EMR
  • AppState: Application state and session information
  • Clinical Resources: As metadata for data provenance
  • AuditEvent: For tracking EMR-related activities

Technical Considerations

Important aspects:

  • Non-instance-specific identifiers for EMR products
  • Version strings may follow vendor-specific formats
  • Multiple instances may exist for multi-site deployments
  • Supports both commercial and custom EMR systems