Difference between revisions of "Transport Pattern Mapping"

From IHE Wiki
Jump to navigation Jump to search
Line 4: Line 4:
 
** http://www.omg.org/spec/HData/1.0/PDF/
 
** http://www.omg.org/spec/HData/1.0/PDF/
 
** on first inspection, it does not seem to cause incompatibility issues with existing use of REST in MHD.
 
** on first inspection, it does not seem to cause incompatibility issues with existing use of REST in MHD.
** the recommendation of using CORS has impact on HTTP level: http://enable-cors.org/. Discussed in http://www.hl7.org/implement/standards/fhir/security.html
+
* the recommendation of using CORS has impact on HTTP level: http://enable-cors.org/. Discussed in http://www.hl7.org/implement/standards/fhir/security.html
 +
 
 +
== HTTP verbs used for basic operations on resources in FHIR ==
 +
* POST - create
 +
* PUT - update
 +
* DELETE - delete
 +
* GET - read
 +
 
 +
There are some exceptions to this scheme: the "transaction" operation utilizes POST to create or update a set of resources (resource bundle) atomically.
 +
 
 +
== Mapping of FHIR operations to existing XDS transactions ==
 +
 
 +
=== Transaction operation ===
 +
This operation can facilitate Provide & Register Document Set-b (ITI-41, ITI-42) and "Update Document Set" (ITI-57) transactions. It can create and update a set of resources (authors, documents) in one transaction:
 +
* If entry.content is omitted, the resulting operation is closer to Register (ITI-42).
 +
* If entry.id refers to an existing resource, it mimicks "Update Document Set"

Revision as of 06:45, 18 July 2014

FHIR-MHD Transport Pattern Mapping Notes

HTTP verbs used for basic operations on resources in FHIR

  • POST - create
  • PUT - update
  • DELETE - delete
  • GET - read

There are some exceptions to this scheme: the "transaction" operation utilizes POST to create or update a set of resources (resource bundle) atomically.

Mapping of FHIR operations to existing XDS transactions

Transaction operation

This operation can facilitate Provide & Register Document Set-b (ITI-41, ITI-42) and "Update Document Set" (ITI-57) transactions. It can create and update a set of resources (authors, documents) in one transaction:

  • If entry.content is omitted, the resulting operation is closer to Register (ITI-42).
  • If entry.id refers to an existing resource, it mimicks "Update Document Set"