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.
TypedFhir API / C#
The typed accessor surface Device exposes for Device — generated from this IG's compiled profile; each typed accessor has a validating raw-FHIR twin (xRaw) where marked. The three ports are parity-enforced.
class Device : ClinicalResource — generated source
| Accessor | Type | Access | Notes |
|---|---|---|---|
| EffectiveDate | FuzzyDate? |
read-only | The resource's effective date — the first present of this profile's date elements (precedence), normalized to the canonical FuzzyDatetime f… |
| Display | string? |
read-only | The resource's human headline — a coded concept's label, else a title / name, else undefined. |
| Status | string? |
read/write | active | inactive |
| StatusReason | Concepts |
read/write · raw twin | online | paused | standby | offline | not-ready | transduc-discon | hw-discon | off |
| Manufacturer | string? |
read/write | App developer/company (optional) |
| DeviceName | Json[]? |
read/write | The name of the device as given by the manufacturer |
| Type | Concept? |
read/write · raw twin | Software application type |
| Note | Notes |
read/write | Brief description of the app |