1 / 6

RESTful Roadmap

RESTful Roadmap. Brief Profile Proposal for 2014/15 presented to the IT Infrastructure Planning Committee R Horn (Agfa Healthcare). Problem to be solved. IHE and ITI lack a roadmap for creating RESTful alternatives to current profiles.

alia
Download Presentation

RESTful Roadmap

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. RESTful Roadmap Brief Profile Proposal for 2014/15 presented to the IT Infrastructure Planning Committee R Horn (Agfa Healthcare)

  2. Problem to be solved • IHE and ITI lack a roadmap for creating RESTful alternatives to current profiles. • IHE and ITI lack a pattern for creating new RESTful profiles. • IHE and ITI are receiving workitem proposals for specific transactions with RESTful requirements. • IHE Radiology already has workitems defining RESTful transactions are part of their imaging, reporting, and radiation dose profiles. • ITI received three workitem proposals for RESTful profiles, and some other workitems may involve RESTful transactions. • ITI already has several RESTful profiles in TI (MHD, IUA, and CSD)

  3. External Requirements • The RESTful stack capabilities of mobile devices and browser applications are limited. The profiles must work within those constraints. • This is an external constraint. • This constraint affects DICOM, HL7, and others. • There is no industry consensus on what the precise constraints are, although best practices documents are emerging. • The RESTful roadmap needs to co-exist and coordinate with HL7 and DICOM activities. • HL7 RESTful activity is primarily FHIR at present. It is now being spread across more of HL7 activities. • DICOM is publishing a series of supplements and creating workitems that are mapping existing services onto RESTful transports. This is a work in progress, but most of the SOP instance transfer services are now defined for both original DIMSE and RESTful transports. Work is moving to other DICOM transactions.

  4. Proposed Standards & Systems • The whitepaper will need to: • Identify and characterize IHE profiles that are candidates for RESTful transport. The characterization should include an evaluation of the differences between current transports and RESTful transports. • Identify and characterize the expected RESTful activities of DICOM, HL7, and other standards that are profile. • Provide an index for the profiles that summarizes • Likely workload for each transaction or profile • Interactions and dependencies on other profiles and external standards activities

  5. Profile Structure • This whitepaper will be an engineering evaluation of approaches, work estimates, and dependencies for IHE profiles. It will avoid scheduling and prioritization, because those are subject to market change and should be informed by the engineering evaluation. • Rather than make forecasts about future schedules of other standards organizations, it will just establish the dependencies between other organization efforts and IHE efforts.

  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)

More Related