Skip to content

App Device Profile

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

Simple profile for applications that integrate with patient data and require consent tracking. Contains just the essential information: app name, client_id, and basic details.

Elements / Differential

What this profile constrains beyond Device. Anything not listed is unchanged from the base; muted type/cardinality values are the base's, shown for context.

Element Flags Card. Type Description & Constraints
Device Invariants: nexus-note-extension-not-where-native
meta 0..1 Meta
source S 0..1 uri Identifies EMR instance & pipeline version the resource came from i
identifier 0..* Identifier App identifier (include OAuth client_id) i
status S 1..1 code active | inactive i
manufacturer S 0..1 string App developer/company (optional)
deviceName S 1..1 BackboneElement
name S 1..1 string Simple app name
type S 0..1 CodeableConcept Software application type
note S 0..1 Annotation Brief description of the app