(270 intermediate revisions by 21 users not shown)
Line 1:
Line 1:
[[Image:UnderConstructionBar.gif]]
[[Image:IHE_LOGO_New.jpg|left]]'''The IT Infrastructure Domain''' supplies infrastructure for sharing healthcare information. An ''infrastructure interoperability component'' represents a common IT function that is used as a building block for a variety of use cases... a necessary ingredient, but rarely visible to the end user!! These components may be embedded in an application, but are often deployed as a shared resource within a Health Information Exchange.
'''IHE IT Infrastructure''' addresses underlying Information Technology issues that can be used by other IHE domains.
This domain began in 2003, is sponsored by [http://www.himss.org/ASP/topics_ihe.asp Health Information Management Systems Society (HIMSS)]. The ITI domain [[Profiles#IHE_IT_Infrastructure_Profiles|Profiles]] are fully described in the [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].
IHE IT Infrastructure is sponsored by the [http://www.himss.org/ASP/topics_ihe.asp Health Information Management Systems Society (HIMSS)] and manages the [[Profiles#IHE IT Infrastructure Profiles| IT Infrastructure Profiles]] and the [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].
==Strategy and liaison activity==
This [[ITI_Strategy_and_Liaison_Activity | ITI strategy and liaison activity]] page provides the strategy followed by the IT Infrastructure domain and the liaisons with other domains, SDOs, etc., regarding its area of expertise.
__TOC__
==IT Infrastructure Committees==
==Timeline : 2007-2008 Development Cycle==
:[[ITI Planning Committee]]
:[[ITI Technical Committee]]
Find attached the consolidated input for next week, Dec 5-6th meeting in OakBrook from the Planning Committee to the ITI Tech Committee.{| style="width:100%" border="1" cellpadding="3"
==Current IT Infrastructure Profiles (in Final Text and Trial Implementation)==
See also the [[IT Infrastructure 2005-2006 Development Cycle]]
IT-Infrastructure Profiles (aka Implementation Guides) can be found:
* [[Profiles#IHE_IT_Infrastructure_Profiles|Profiles]] pages on the wiki
* [https://profiles.ihe.net/ITI/TF/Volume1/index.html Profiles] on the IHE Formal Publication site
* [https://github.com/search?q=topic%3Aiti+org%3AIHE&type=repositories Profiles] on the IHE Github
==Roadmap==
==Planning and Development Cycle==
The following outlines the general activities and steps planned for a year.
==Current Activity==
Brief Profile proposals [https://github.com/IHE/IT-Infrastructure/wiki/New-Work-Item-Proposal-process IHE ITI Github Site]
IT-Infrastructure uses [[Continuous Development Process]] so each quarter face-to-face (or virtual) meeting is when milestones can be reached.
Contact the ITI Technical Committee if you would like to participate, or watch for Public Comment drafts in mid-July, 2007.
IT-Infrastructure uses [https://github.com/IHE/IT-Infrastructure/projects/2 Github Kanban board] to track projects. All formal releases are published on https://profiles.ihe.net
==Demonstrations & Presentations==
==Profile Selection==
Presentations are all presented on [https://www.youtube.com/@IHEIntl/videos YouTube in IHE-International]
'''Brief Profile Proposals''' were submitted for the 2007-2008 Development Cycle.
All presentations are also published in PowerPoint form on the [https://github.com/IHE/IT-Infrastructure GitHub repository] in the [https://github.com/IHE/IT-Infrastructure/tree/master/Presentations IHE ITI-Infrastructure presentations folder]
'''Detailed Profile Proposals''' were short-listed during the face to face Planning Committee meeting early November 2007 and further consolidated at the Nov 20th T-con:
==Communication and Marketing==
* Profiles forwarded to the Technical Committee for technical evaluation and sizing (Dec 5-6):
· Technical/Planning Committee to clarify requirements
6. Aggregate Data (Floyd/Charles/ITI Co-Chairs). If clarified in an acceptable manner to be submitted for evaluation to ITI TC (Dec 5th). Otherwise, may have to be downgraded to a White paper.
13. Extensions to XDS for Affinity Domain Metadata (brief proposal to be submitted)
14. Fine-Grained Data Repository
15. Manage User Credentials
16. Research Investigator ID and Authentication
17. Service Registry
18. Terminology Services for Semantic Interoperability
· Referred to other IHE Domains:
19. Advanced Patient Privacy Consents - to PCC Planning Committee
20. Configuration Management - to Connect-a-thon Tooling.
The ITI Technical Committee has evaluated these at dec 5th & 6th Meeting with recommendations for the January 4th T-con of the planning Committee where the final list of supplements to be developped in 2007 are selected.
The Planning Committee will finalize the scope of its White Papers on the January 29th T-con. the Technical Committee is welcome to provide any input or suggestion on these Planning Committee white papers.
These items were '''selected''' by the Planning Committee for this Cycle:
* [[ITI,_PCC_%26_QRPH_Meetings|ITI, PCC & QRPH Development Cycle Meetings]]
* [[Committees]]
This page is based on the [[Domain Template]].
*This page is based on the [[Domain Template]].
[[category: IT Infrastructure]]
[[Category: ITI to do]]
Latest revision as of 10:24, 27 November 2023
The IT Infrastructure Domain supplies infrastructure for sharing healthcare information. An infrastructure interoperability component represents a common IT function that is used as a building block for a variety of use cases... a necessary ingredient, but rarely visible to the end user!! These components may be embedded in an application, but are often deployed as a shared resource within a Health Information Exchange.
This ITI strategy and liaison activity page provides the strategy followed by the IT Infrastructure domain and the liaisons with other domains, SDOs, etc., regarding its area of expertise.
