Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OHF IHE support"
| Line 4: | Line 4: | ||
With the help of the users of OHF in the [[IHE Connectathon 2007]], we are guiding a wish list of profiles and actors in the '''[[OHF IHE support]]''' page. The page details what OHF will/will not/maybe support. Please use the [news||//news.eclipse.org/eclipse.technology.ohf OHF Newsgroup] to comment and ask ask questions about the list. Thanks for Beth of [http||//www.capmedphr.com/ CapMed] for helping with the initial setup of the list. | With the help of the users of OHF in the [[IHE Connectathon 2007]], we are guiding a wish list of profiles and actors in the '''[[OHF IHE support]]''' page. The page details what OHF will/will not/maybe support. Please use the [news||//news.eclipse.org/eclipse.technology.ohf OHF Newsgroup] to comment and ask ask questions about the list. Thanks for Beth of [http||//www.capmedphr.com/ CapMed] for helping with the initial setup of the list. | ||
| − | {| | + | {|style="border-top:1px solid blue;" |
!IHE Actor | !IHE Actor | ||
!General Comments | !General Comments | ||
Revision as of 19:00, 2 August 2006
OHF supports IHE transactions via regular RCP plugins support and even plain Java libraries through the OHF IHE Client plugins, and through Web Services using the OHF Bridge. The OHF Bridge provides a subset of the OHF IHE Client plugins functionalities. It wraps them and expose SOAP calls that are routed to the plugins.
With the help of the users of OHF in the IHE Connectathon 2007, we are guiding a wish list of profiles and actors in the OHF IHE support page. The page details what OHF will/will not/maybe support. Please use the [news||//news.eclipse.org/eclipse.technology.ohf OHF Newsgroup] to comment and ask ask questions about the list. Thanks for Beth of [http||//www.capmedphr.com/ CapMed] for helping with the initial setup of the list.
| IHE Actor | General Comments | Support via plugins APi | Support via Bridge |
|---|---|---|---|
| Patient Care Coordination Technical Framework | |||
| ED Referral (EDR) | Just CDA R2 Implies no action item for OHF? | ||
| Preprocedural History and Physical (PPHP) | just CDA R2 Implies no action item for OHF? | ||
| Exchanging PHR Content (XPHR) | Its the new version of XDS-MS, this is just CDA R2 from our perspective. But it also has some workflow components (ie. vol 1 and vol 2). Still should read for any changes from last year. | ||
| Laboratory Technical Framework | |||
| Sharing Lab Reports (XDS-LAB) | just CDA R2 Implies no action item for OHF? | ||
| IT Infrastructure Technical Framework | |||
| XDS Source | OHF provides functionality | ||
| XDS Consumer | OHF provides functionality | ||
| ATNA Secure Node | OHF provides functionality - actions must be taken in the application and OS | ||
| ATNA Secure Application | OHF provides functionality - actions must be taken in the application and OS | ||
| XDM (media) | this is a profile for a doctor to save patient data on a CD/R or a USB key and give to a patient to give to a specialist (for example). In essence, this profile circumvents any and all infrastructure we provide. They may be able to use the metadata model to create metadata for the files, but that'd be about it. | ||
| XDR (reliable) interchange | this is a profile for a doctor to send (via email attachment) the same information he would to an XDS Repository to another Doctor. XDM require an additional metadata attribute called"intendedRecipient". Again, this circumvents our infrastructure ... but the metadata model and it's extractors/transformers may be of use here. | ||
| Cross-enterprise Scanned Document Sharing (XDS-SD) | just CDA R2 Implies no action item for OHF? | ||
| Document Digital Signature (DSG) | OHF provides functionality (Need to discuss) | ||