Agentforce Health Developer Guide

Agentforce Health Developer Guide
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

EhrDevice__c to CareRegisteredDevice and Asset

Fields in EhrDevice__c map to CareRegisteredDevice and Asset in the Clinical data model.

Fields

Field Details Clinical Data Model Field Notes
Contact​__c
Description
A long text description of the contact details for an organization or person who’s responsible for support for the device.
 Asset.​Asset​Serviced​By The field in the Clinical data model is a lookup to Account, while the EHR data model field is a text field.
Device​URL__c
Description
A long text description of the network address on which the device can be directly contacted.
 ​​Asset.​Product​2Id​.Display​Url N/A
Expiry​__c
Description
The date and time after which this device is not valid or should not be used.
 Asset.​Usage​End​Date
IsRestricted​__c
Description
Indicates whether or not this field has restricted visibility based on sharing rules.
 Not Suppoted N/A
IsVisible​OnPatient​Card__c
Description
Indicates whether or not this field appears on the patient card.
 Not Suppoted N/A
Location255​__c
Description
Where the device is found. Can be a literal location (for example, GPS coordinates), a logical place (for example, “with the patient”), or a coded location. Limit: 255 characters.
 Not Suppoted N/A
Location​__c
Description
A long text description of where the device is found. Can be a literal location (for example, GPS coordinates), a logical place (for example, “with the patient”), or a coded location.
 Not Suppoted N/A
LotNumber​__c
Description
A lot number assigned by the manufacturer.
 Not Suppoted Even though lot number is not supported, the Clinical data model supports serial numbers using the Asset.​Serial​Number field.
Manufacturer​__c
Description
The name of the device’s manufacturer.
 ​​Asset.​Asset​Provider​By The Clinical data model field is a lookup to Account while the EHR data model field is a stringn field.
Model​__c
Description
An identifier that’s assigned by the manufacturer to identify the product by its type. This number is shared by the all devices that are sold as the same type.
 Asset​.Product​Code N/A
Name
Description
The EHR device ID. Limit: 255 characters.
 ​​Care​Registered​Device​​.Name ID values are recommended to be stored using the Identifier object.
Owner255​__c
Description
The organization that’s responsible for the provision and maintenance of the device. Limit: 255 characters.
 Asset.​Asset​Serviced​By The field in the Clinical data model is a lookup to Account, while the EHR data model field is a text field.
Owner__c
Description
The long text description of the organization that’s responsible for the provision and maintenance of the device.
 Asset.​Asset​Serviced​By The field in the Clinical data model is a lookup to Account, while the EHR data model field is a text field.
Patient__c
Description
The patient’s name. Lookup to EhrPatient__c.
 Care​Registered​Device​​.PatientId The clinical data model field references a Person Account.
Source​SystemId​__c
The ID of the record in the source system.
 Care​Registered​Device​​.Source​System​Identifier N/A
Source​System​Modified​__c
The date and time when the record was last modified in the source system.
 Not supported N/A
Type​__c
Description
The type of device.
 ​​Care​Registered​Device​.Device​TypeId The Clinical data model field is a reference to a code set while the EHR data model field is a string field.
Udi__c
Description
The United States Food and Drug Administration-mandated Unique Device Identifier (UDI). Use the human-readable information (the content that the user sees, which sometimes differs from the syntax in the barcode). The unique identifier can identify an instance of a device uniquely or just identify the type of the device. The DI part can be extracted from the UDI when required and used to find information about the device through the GUDID.
 Care​Registered​Device​​.Unique​Device​Id1, Care​Registered​Device​​.Unique​Device​Id2, and Care​Registered​Device​​.Unique​Device​Id3 The Clinical data model supports specifying up to 3 UDIs for a device, with the supported metadata types being the device identifier and device issuer.
Care​Registered​Device​​.Unique​Device​Id1​Issuer, Care​Registered​Device​​.Unique​Device​Id2Issuer, and Care​Registered​Device​​.Unique​Device​Id3Issuer
Version​__c
Description
The version of the device, if the device has multiple releases under the same model, is software, or carries firmware.
 Not supported N/A