MedicalDevice class
- Available Extensions
Constructors
-
MedicalDevice({String? id, String? rev, int? deletionDate, List<
Identifier> identifiers = const [], int? created, int? modified, String? author, String? responsible, Set<CodingReference> labels = const {}, Set<CodingReference> codes = const {}, int? endOfLife, String? externalId, String? name, String? type, String? brand, String? model, String? serialNumber, String? parentId, List<String> picture = const [], Set<Property> properties = const {}, SystemMetaDataOwner? systemMetaData}) - Returns a new MedicalDevice instance.
Properties
-
The id of the User that created this medical device. When creating the device, this field will be filled automatically by the current user id if not provided.
read / write
- brand ↔ String?
-
Brand of the device recording the data
read / write
-
codes
↔ Set<
CodingReference> -
A code is an item from a codification system that qualifies the content of this medical device. SNOMED-CT, ICPC-2 or ICD-10 codifications systems can be used for codes
read / write
- created ↔ int?
-
the creation date of the medical device (encoded as epoch).
read / write
- deletionDate ↔ int?
-
the soft delete timestamp. When a medical device is ”deleted“, this is set to a non null value: the moment of the deletion
read / write
- endOfLife ↔ int?
-
Soft delete (unix epoch in ms) timestamp of the medical device
read / write
- externalId ↔ String?
-
An external (from another source) id with no guarantee or requirement for unicity.
read / write
- hashCode → int
-
The hash code for this object.
read-onlyoverride
- id ↔ String?
-
The Id of the MedicalDevice. We encourage using either a v4 UUID or a HL7 Id.
read / write
-
identifiers
↔ List<
Identifier> -
Typically used for business / client identifiers. An identifier should identify a device uniquely and unambiguously. However, iCure can't guarantee the uniqueness of those identifiers : This is something you need to take care of.
read / write
-
labels
↔ Set<
CodingReference> -
A label is an item from a codification system that qualifies a medical device as being member of a certain class, whatever the value it might have taken. If the label qualifies the content of a field, it means that whatever the content of the field, the label will always apply. LOINC is a codification system typically used for labels.
read / write
- model ↔ String?
-
Model of the device recording the data
read / write
- modified ↔ int?
-
the last modification date of the medical device (encoded as epoch).
read / write
- name ↔ String?
-
Name of the device/application recording the data
read / write
- parentId ↔ String?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
read / write
-
picture
↔ List<
String> -
Picture of the device/application
read / write
-
properties
↔ Set<
Property> -
read / write
- responsible ↔ String?
-
The id of the data owner that is responsible of this medical device. When creating the medical device, will be filled automatically by the current user data owner id (HealthcareProfessional, Patient or MedicalDevice) if missing
read / write
- rev ↔ String?
-
the revision of the medical device in the database, used for conflict management / optimistic locking.
read / write
- runtimeType → Type
-
A representation of the runtime type of the object.
read-onlyinherited
- serialNumber ↔ String?
-
Serial number of the device recording the data
read / write
- systemMetaData ↔ SystemMetaDataOwner?
-
Please note: This property should have been non-nullable! Since the specification file
does not include a default value (using the "default:" property), however, the generated
source code must fall back to having a nullable type.
Consider adding a "default:" property in the specification file to hide this note.
read / write
- type ↔ String?
-
Type of device/application recording the data. (eg. "smartphone", "watch",...)
read / write
Methods
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a nonexistent method or property is accessed.
inherited
-
toJson(
) → Map< String, dynamic> -
toString(
) → String -
A string representation of this object.
override
Operators
-
operator ==(
Object other) → bool -
The equality operator.
override
Static Methods
-
fromJson(
dynamic value) → MedicalDevice? -
Returns a new MedicalDevice instance and imports its values from
value
if it's a Map, null otherwise. -
listFromJson(
dynamic json, {bool growable = false}) → List< MedicalDevice> ? -
mapFromJson(
dynamic json) → Map< String, MedicalDevice> -
mapListFromJson(
dynamic json, {bool growable = false}) → Map< String, List< MedicalDevice> >
Constants
-
requiredKeys
→ const Set<
String> -
The list of required keys that must be present in a JSON.
<String>{'identifiers', 'labels', 'codes', 'properties'}