App Device Profile

Canonical	../StructureDefinition/nexus-emr-core-appdevice
Status	draft · 1.26.0
Base	Device (constraint)
Source	FSH · 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.

Examples

Alberta Diabetes Research Portal · SmartDocs AI Scribe App · WellnessTracker Pro App

WellnessTracker Pro App

Personal wellness monitoring app - CONSENT DENIED by Avery

Device/wellness-tracker-pro — claims conformance to App Device Profile

{
  "resourceType": "Device",
  "id": "wellness-tracker-pro",
  "meta": {
    "profile": [
      "../StructureDefinition/nexus-emr-core-appdevice"
    ]
  },
  "text": {
    "status": "generated",
    "div": "<div xmlns="http://www.w3.org/1999/xhtml"><p><b>WellnessTracker Pro</b></p><p>Comprehensive wellness monitoring and lifestyle coaching app. Client ID: wellness-tracker-prod-v2</p></div>"
  },
  "identifier": [
    {
      "system": "../NamingSystem/nexus-emr-appdevice-identifier",
      "value": "wellness-tracker-pro"
    },
    {
      "system": "https://oauth.example.com/client-registry",
      "value": "wellness-tracker-prod-v2",
      "use": "secondary"
    }
  ],
  "status": "active",
  "deviceName": [
    {
      "name": "WellnessTracker Pro",
      "type": "user-friendly-name"
    }
  ],
  "manufacturer": "HealthTech Innovations Inc",
  "type": {
    "text": "Personal Health Monitoring App"
  },
  "note": [
    {
      "text": "Personal wellness application that tracks vitals, medications, and lifestyle factors to provide coaching recommendations."
    }
  ]
}

Referenced by: Nexus EMR App Consent - DENIED Example