Sorry for the nit-picking here. In a very literal way RESTful FHIR is not CRUD "on a database", because each FHIR CRID operation is translated through a series of internal APIs which likely do things other than the initial simple CRUD operation – for example, no EHR will actually delete a patient's record upon receiving a FHIR patient delete.

Existing Wording:

These RESTful APIs are great for CRUD operations on a database, but they don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

Proposed Wording:

These RESTful APIs are great for CRUD operations, but they don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.