FHIR Exchange Mechanisms Flashcards

This section is expected to have 14% of total questions in certification test

1
Q

What are the commonly available FHIR exchange methods?

A
  1. REST (Widely used)
  2. Documents
  3. Messages
  4. Services
  5. Databases
  6. Bulk Data Upload
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

True or False: ResourceID should be unique across resources

A

False.
FHIR specification indicates that the ResourceID should be unique for each type of resources. Not across all resources.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

REST: What are the Instance level interactions?

A
  1. read - Read the current state of the resource
  2. vread - Read the state of a specific version of the resource
  3. update - Update an existing resource by its id (or create it if it is new)
  4. patch - Update an existing resource by posting a set of changes to it
  5. delete - Delete a resource
  6. history - Retrieve the change history for a particular resource
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

REST: What are the Type level interactions?

A
  1. create - Create a new resource with a server assigned id
  2. search - Search the resource type based on some filter criteria
  3. history - Retrieve the change history for a particular resource type
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

REST: What are the Whole System Interactions?

A
  1. capabilities - Get a capability statement for the system
  2. batch/transaction - Update, create or delete a set of resources in a single interaction
  3. search - Search across all resource types based on some filter criteria
  4. history - Retrieve the change history for all resources
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

REST: What are the MIME types supported by FHIR?

A
  1. XML - application/fhir+xml
  2. JSON - application/fhir+json
  3. RDF - application/fhir+turtle (only the Turtle format is supported)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

REST: Is application/json+fhir a valid MIME type for FHIR?

A

Yes.

Even though the current recommended MIME is fhir+json, previously used json+fhir is still valid

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

REST: What is a Service Base URL?

A

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}

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

REST: List the possible interactions using the verb GET

A
  1. read
  2. vread
  3. capabilities
  4. search
  5. history
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

REST: List the possible interactions using the verb POST

A
  1. create
  2. batch/transaction
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

REST: List the possible interactions using the verb PATCH

A

patch

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

REST: List the possible interactions using the verb PUT

A

update

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

REST: List the possible interactions using the verb DELETE

A

delete

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

REST: What verb you may use to perform a Search

A

GET

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

REST: What verb you may use to perform a Create transaction

A

POST (Servers MAY choose to allow clients to use PUT too)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

REST: What verb you may use to retrieve a particular resource

A

GET

17
Q

REST: What happens during a PUT transaction?

A

FHIR server would create a new version of the specified resource with the new information sent via the request

18
Q

REST: What are the transaction processing order?

A

DELETE > POST > PUT/PATCH > GET/ HEAD > Conditional

  1. Process any DELETE interactions
  2. Process any POST interactions
  3. Process any PUT or PATCH interactions
  4. Process any GET or HEAD interactions
  5. 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.

19
Q

REST: Is it mandatory to support _history?

A

No

20
Q

REST: What resource will be returned after a DELETE operation?

A

OperationOutcome

21
Q

REST: Can a resource still be accessed after a DELETE operation?

A

Yes – Using _history operation if implemented by the server

22
Q

REST: What is a conditional update?

A

Use parameters to search for a resource to update during a PUT rather than sending a specific id

23
Q

REST: How do you perform a conditional create?

A

Use If-None-Exist header parameter during POST to verify if the resource exists before creating as new