1 / 6

OAuth Profile

OAuth Profile. Brief Profile Proposal for 2014/15 presented to the IT Infrastructure Planning Committee R Horn (Agfa Healthcare). Problem to be solved. XDW and the XDW based profiles provide a valuable workflow service, but require systems that support the SOAP and WS-* stack.

tino
Télécharger la présentation

OAuth Profile

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OAuth Profile Brief Profile Proposal for 2014/15 presented to the IT Infrastructure Planning Committee R Horn (Agfa Healthcare)

  2. Problem to be solved • XDW and the XDW based profiles provide a valuable workflow service, but require systems that support the SOAP and WS-* stack. • Mobile health devices (browser apps, smartphones, tablets, etc.) do not support the SOAP and WS-* stack. They support the RESTful HTTP stack. • Mobile health devices are presently unable to take advantage of the XDW and XDW based profiles.

  3. External Requirements • The RESTful stack capabilities of mobile devices are limited. The profile must work within those constraints. • This is a common constraint. The MHD profile and efforts in other standards organizations like HL7 and DICOM are also addressing this constraint. • This profile must work within the same family of actors and profiles as the current XDW and XDW derived profiles.

  4. Proposed Standards & Systems • This will be very similar to the MHD profile. The following issues must be considered: • Evaluate whether any extensions to MHD are needed to deal with issues of updating workflow documents and adding supporting documents. Some of the MHD restrictions may need to be relaxed. • Evaluate whether there are any issues to be resolved with schema, etc. for the documents. (A lossless JSON automatic translation has been suggested.)

  5. Profile Structure • This profile will probably be an option to XDW profile to add RESTful transactions.

  6. Discussion • What level of effort do you foresee in developing this profile? • Small to Moderate work effort. • Is there someone who is willing to act as profile editor? • Rob Horn (Agfa), with Brad Generaux (Agfa) • Should this workitem be extended to include a more formal evaluation of the other ITI profiles to evaluate the level of effort needed to create RESTful options for the other profiles.

More Related