API end point: https://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir-r4.

Resource Device (R4)

Maps CareEvolution DeviceDataSource concept describing devices.

Supported interactions

• read
• search
• create
• update
• delete

Search parameters

Name	Type	Modifiers , prefixes	Multiple values	Can be chained	Description
_id	Token		Yes		See here
patient	Reference	:missing	Yes	Yes	Patient information, if the resource is affixed to a person
type	Token	:not :in :not-in :missing	Yes		The type of the device
udi-carrier	String	:contains :exact :missing	Yes		UDI Barcode (RFID or other technology) string in HRF format.
udi-di	String	:contains :exact :missing	Yes		The udi Device Identifier (DI)

Sorts

• _id

Supports multiple sorts

Includes

• patient
• Observation:device
• Provenance:target

Operations

• validate - Validate a resource

To FHIR mappings

FHIR	CareEvolution
distinctIdentifier	Property('DistinctIdentifier')
expirationDate	Property('ExpirationDate')
identifier	Identifier
lotNumber	Property('LotNumber')
manufactureDate	Property('ManufactureDate')
patient	PatientID
serialNumber	Property('SerialNumber')
status Bindings:  valueset-device-status	Status Domain: DeviceDataSourceStatus
type	TypeTerm Domain: DeviceDataSourceType
udiCarrier.carrierAIDC	CarrierAIDC
udiCarrier.carrierHRF	UdiCarrierHRF
udiCarrier.deviceIdentifier	UdiDeviceIdentifier

From FHIR mappings

FHIR	CareEvolution
distinctIdentifier	Property('DistinctIdentifier')
expirationDate	Property('ExpirationDate')
id	Identifier
identifier	Identifier
lotNumber	Property('LotNumber')
manufactureDate	Property('ManufactureDate')
patient	PatientID
serialNumber	Property('SerialNumber')
status Bindings:  valueset-device-status	Status Domain: DeviceDataSourceStatus
type	TypeTerm Domain: DeviceDataSourceType
udiCarrier.carrierAIDC	CarrierAIDC
udiCarrier.carrierHRF	UdiCarrierHRF
udiCarrier.deviceIdentifier	UdiDeviceIdentifier

---