Transport Pattern Mapping: Difference between revisions
Jump to navigation
Jump to search
WalcoVanLoon (talk | contribs) No edit summary |
WalcoVanLoon (talk | contribs) No edit summary |
||
| 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 | |||
Revision as of 08:21, 27 June 2014
FHIR-MHD Transport Pattern Mapping Notes
- FHIR REST API (in least in theory) is based on OMG Health RESTful specification
- 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.
- 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