FHIR Exchange Mechanisms Flashcards
This section is expected to have 14% of total questions in certification test
What are the commonly available FHIR exchange methods?
- REST (Widely used)
- Documents
- Messages
- Services
- Databases
- Bulk Data Upload
True or False: ResourceID should be unique across resources
False.
FHIR specification indicates that the ResourceID should be unique for each type of resources. Not across all resources.
REST: What are the Instance level interactions?
- read - Read the current state of the resource
- vread - Read the state of a specific version of the resource
- update - Update an existing resource by its id (or create it if it is new)
- patch - Update an existing resource by posting a set of changes to it
- delete - Delete a resource
- history - Retrieve the change history for a particular resource
REST: What are the Type level interactions?
- create - Create a new resource with a server assigned id
- search - Search the resource type based on some filter criteria
- history - Retrieve the change history for a particular resource type
REST: What are the Whole System Interactions?
- capabilities - Get a capability statement for the system
- batch/transaction - Update, create or delete a set of resources in a single interaction
- search - Search across all resource types based on some filter criteria
- history - Retrieve the change history for all resources
REST: What are the MIME types supported by FHIR?
- XML - application/fhir+xml
- JSON - application/fhir+json
- RDF - application/fhir+turtle (only the Turtle format is supported)
REST: Is application/json+fhir a valid MIME type for FHIR?
Yes.
Even though the current recommended MIME is fhir+json, previously used json+fhir is still valid
REST: What is a Service Base URL?
The Service Base URL is the address where all of the resources defined by this interface are found.
All the logical interactions are defined relative to the service base URL.
The Service Base URL takes the form of http{s}://server{/path}
REST: List the possible interactions using the verb GET
- read
- vread
- capabilities
- search
- history
REST: List the possible interactions using the verb POST
- create
- batch/transaction
REST: List the possible interactions using the verb PATCH
patch
REST: List the possible interactions using the verb PUT
update
REST: List the possible interactions using the verb DELETE
delete
REST: What verb you may use to perform a Search
GET
REST: What verb you may use to perform a Create transaction
POST (Servers MAY choose to allow clients to use PUT too)
REST: What verb you may use to retrieve a particular resource
GET
REST: What happens during a PUT transaction?
FHIR server would create a new version of the specified resource with the new information sent via the request
REST: What are the transaction processing order?
DELETE > POST > PUT/PATCH > GET/ HEAD > Conditional
- Process any DELETE interactions
- Process any POST interactions
- Process any PUT or PATCH interactions
- Process any GET or HEAD interactions
- Resolve any conditional references
*If any resource identities (including resolved identities from conditional update/delete) overlap in steps 1-3, then the transaction SHALL fail.
REST: Is it mandatory to support _history?
No
REST: What resource will be returned after a DELETE operation?
OperationOutcome
REST: Can a resource still be accessed after a DELETE operation?
Yes – Using _history operation if implemented by the server
REST: What is a conditional update?
Use parameters to search for a resource to update during a PUT rather than sending a specific id
REST: How do you perform a conditional create?
Use If-None-Exist header parameter during POST to verify if the resource exists before creating as new
