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"
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | 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| OHF Bridge]]. | + | Content on this page has been removed because it was inaccurate and out of date. More information about OHF support for IHE profiles can be found here: [[OHF IHE]]. |
| − | The [[Ohf bridge| OHF Bridge]] provides a subset of the [[OHF IHE Client plugins]] | + | |
| + | |||
| + | <!--[[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| OHF Bridge]]. | ||
| + | The [[Ohf bridge| OHF Bridge]] provides a subset of the [[OHF IHE Client plugins]] functionalists. It wraps them and expose SOAP calls that are routed to the plugins. | ||
| + | |||
| + | With the help of users who intends to use [[OHF]] in the [[IHE Connectathon 2007]], we are gathering a wish list of profiles and actors in the following table page. The table details what [[OHF]] will/will not/maybe support. Please use the [news://news.eclipse.org/eclipse.technology.ohf OHF Newsgroup] to comment and 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:1px solid blue;" | {|style="border:1px solid blue;" | ||
| Line 12: | Line 17: | ||
! colspan="4" style="background:#ffdead;" | Patient Care Coordination Technical Framework | ! colspan="4" style="background:#ffdead;" | Patient Care Coordination Technical Framework | ||
|- | |- | ||
| − | |ED Referral (EDR) || Just CDA R2 ''Implies no action item for OHF?'' | + | |ED Referral (EDR) || Just CDA R2 ''Implies no action item for OHF?''||Need to discuss||Need to discuss |
|- | |- | ||
| − | |Preprocedural History and Physical (PPHP)|| just CDA R2 ''Implies no action item for OHF?'' | + | |Preprocedural History and Physical (PPHP)|| just CDA R2 ''Implies no action item for OHF?''||Need to discuss||Need to discuss |
|- | |- | ||
| − | |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. | + | |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.||Need to discuss||Need to discuss |
|- | |- | ||
!colspan="4" style="background:#ffdead;" | Laboratory Technical Framework | !colspan="4" style="background:#ffdead;" | Laboratory Technical Framework | ||
|- | |- | ||
| − | |Sharing Lab Reports (XDS-LAB)|| just CDA R2 ''Implies no action item for OHF?'' | + | |Sharing Lab Reports (XDS-LAB)|| just CDA R2 ''Implies no action item for OHF?''||Need to discuss||Need to discuss |
|- | |- | ||
!colspan="4" style="background:#ffdead;" | IT Infrastructure Technical Framework | !colspan="4" style="background:#ffdead;" | IT Infrastructure Technical Framework | ||
|- | |- | ||
| − | |XDS Source|| OHF provides functionality | + | |XDS Source|| OHF provides functionality|| Full support||Does not support folders and multi documents upload |
| + | |- | ||
| + | |XDS Consumer|| OHF provides functionality|| Full support||Does not support the full spectrum of search capabilities. Currently has only a "get all the patient's documents" search, will be enhanced. | ||
|- | |- | ||
| − | | | + | |ATNA Secure Node|| OHF provides functionality - actions must be taken in the application and OS||Need to discuss||Need to discuss |
|- | |- | ||
| − | |ATNA Secure | + | |ATNA Secure Application|| OHF provides functionality - actions must be taken in the application and OS||Need to discuss||Need to discuss |
|- | |- | ||
| − | | | + | |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.||Need to discuss||Need to discuss |
|- | |- | ||
| − | | | + | |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.||Need to discuss||Need to discuss |
|- | |- | ||
| − | | | + | |Cross-enterprise Scanned Document Sharing (XDS-SD)|| just CDA R2 ''Implies no action item for OHF?''||Full support |
|- | |- | ||
| − | | | + | |Document Digital Signature (DSG)|| OHF provides functionality||Need to discuss||Need to discuss |
|- | |- | ||
| − | | | + | |Basic Patient Privacy Consent (BPPC)||Need more info here||Need to discuss||Need to discuss |
|} | |} | ||
| + | --> | ||
Latest revision as of 19:21, 9 October 2007
Content on this page has been removed because it was inaccurate and out of date. More information about OHF support for IHE profiles can be found here: OHF IHE.