Page Comparison

Generic data read/write

• single-enterprise

• atomic Tx ok

• usually app-driven

• granular content

• assumed persistence

CRUD

• C2B, B2B

• decomposed content

• Tx applies to atom

FHIR REST

low volume -> FHIR REST
high volume -> Bulk data

‘multi-CRUD’ possible

Resource-based

Aggregated data exchange

• x-enterprise

• want to commit N items as a single operation

• avoid fragmentation issues

• no assumed accessibility

• opaque content

Business object

• receive a set of included parts as single Tx

FHIR Document API

FHIR document

Business-level service

• business specific i/f

• processing semantics

• transparent content

Transactional service

• often C2B

• end-end comms

• closer to business view

FHIR Operation(s)

• multiple end-points

• may use Parameter resource

• more granular

FHIR Operation(s)

• transactional Bundle (i.e. ACID semantics)

• batch Bundle (non-Tx)
  

Querying

• match criteria-based

Query service

• C2B

FHIR REST search
(query-related)

?applications

Bundle (= set of Resource instances)

Messaging i/f or system

• non-peer-peer

• system-system (non-app)

• routing (post) model

• minimised exchange

• consolidated content

• business semantics = provide / process / respond

Messaging

• B2B

• async

• routing comms model

n/a

FHIR messaging

• simulates v2, v3 msg

• Bundle of type message

• header w/ trigger events

all