xip开发应用-nema(dicom).PPT

  1. 1、本文档共24页,可阅读全部内容。
  2. 2、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
xip开发应用-nema(dicom)

* Language independence – the API is defined in such a way that programs written in any common programming language could utilize it. Platform independence – the API is defined in such a way that it is not dependent on any particular computing platform or operating system. Extensible – the API can be extended in a backwards compatible fashion. Old applications still work even with new extensions in place, while new applications that are aware of the extensions can gain access to a richer set of functionality. Protected – the API design insures that intellectual property rights can be protected, and that appropriate permissions and licenses are in place. In other words, a Hosting System will be able to launch a Hosted Application without being able to ‘see’ the internals of that Hosted Application, nor will the Hosted Application be able to steal internal code of the Hosting System. The Hosting System would not be able to launch a Hosted Application without permission or license from the owner of the Hosted Application. Secure – the Hosted Application’s access to data on the Hosting System would be controlled via the API by the Hosting System. The Hosting System would be responsible for access controls and audit logging, since it is the one providing the data to the Hosted Application * For those of you that were not able to attend Fred Prior’s talk, I’ll first desc Lawrence Tarbox, Ph.D. Washington University in St. Louis School of Medicine Mallinckrodt Institute of Radiology, Electronic Radiology Lab 应用托管 DICOM标准工作组23号,希望从根本上改变了该医学影像世界在关于向分布和部署的医学影像应用的传统思维。 现状 医学影像工作站,一般都是封闭的系统。 目前尚没有没有通用规范的方法来把新的功能加入一个医学工作站。 关键的获益者,那些希望看到新的功能的人,往往不是工作站提供商。 新的‘酷’的工具往往需要把整个工作站加到一个系统中。 从SIIM 2007年工作流程演示 心肺流程 – Dr. Anwer Quershi “… …在各种工作站和不同的设备之间来回穿梭,干扰和减慢治疗… …” Nuclear Workflow – Dr. Eliot Siegel “ … …这一案例说明了多个系统之间的来回交换会引入新的干扰。 … … ?一个全新的世界 将基础平台的提供从应用中分离出来: 基础平台供应商专注于数据与及结果的转移和储存,和对工作流程的管理。 应用提供商专注于处理和分析数据,并且把结果返回到基础平台。 尽量减少重塑车轮 。 ?建议的解决办法 创造一种机制,使得一方产生的应用可以被其他多方生成的系

文档评论(0)

2105194781 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档