(243 intermediate revisions by 18 users not shown)
Line 1:
Line 1:
[[Image:IHE_LOGO_Thumb.jpg|left]]'''The IT Infrastructure Domain''' supports profiles which supply the necessary 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 imbedded in an application, but are often deployed as a shared resource within a RHIO or Health Information Exchange.
[[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.
This domain began in 2003, is sponsored by the [http://www.himss.org/ASP/topics_ihe.asp Health Information Management Systems Society (HIMSS)], and currently supports '''18''' [[Profiles#IHE IT Infrastructure Profiles| IT Infrastructure Profiles]] as well as the [[Frameworks#IHE IT Infrastructure Technical Framework| IT Infrastructure Technical Framework]].
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]].
[[Image:ITI_Overview.jpg|frame|center]]
==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.
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
===2007-2008 Work Plan===
==Planning and Development Cycle==
:'''Profiles'''
The following outlines the general activities and steps planned for a year.
:*Web Services Transport for XDS
:*Cross-Community Access
:*PIX and PDQ using HL7v3 and Web Services
:*Cross-Enterprie User Authentication (Phase 1)
:'''White Papers'''
Brief Profile proposals [https://github.com/IHE/IT-Infrastructure/wiki/New-Work-Item-Proposal-process IHE ITI Github Site]
:*Security Risk Managment
:*Web Services Roadmap
:*Configuration Management
:*Aggregate Data
:*Meeting Privacy Principles using IHE Profiles
===2008-2009+ Profile Candidates===
IT-Infrastructure uses [[Continuous Development Process]] so each quarter face-to-face (or virtual) meeting is when milestones can be reached.
:'''Continue Prior Profile Work'''
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
:*Web Services and SOA for Healthcare
:*Cross-Community Location
:*Cross-Enterprise User Authentication (Phase 2)
:'''Advance White Papers to Profiles'''
:*Aggregate Data Monitoring
:*Configuration Management
===2008-2009+ Profile Candidates===
:*Cross-Enterprise Ordering
:*Cross-Enterprise Workflow Scheduling
:*XDS Affinity Domain Configuration
:*XDS Templates
:*Composite Documents
:*Role-Based Access Control
:*Anonymization and Pseudonymization
:*Mobile Security
:*Master File Maintenance
:*Service Discovery
:*SNMP MIB's
==Current Activity==
Contact the [[ITI Planning Committee]] or the [[ITI Technical Committee]] if you would like to participate, or watch for '''public comment''' drafts in mid-June, 2007.
==Profile Selection==
'''Brief Profile Proposals''' were submitted for the 2007-2008 Development Cycle.
'''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:
'''Profiles forwarded to the Technical Committee for technical evaluation and sizing (Dec 5-6):'''
2. [[Cross-Enterprise User Authentication (XUA)]] : Tech Editor: John Moehrke
3. [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Planning_Cmte/Detailed%20Profile%20Proposals/IHE-XDS-MTOM-Detailed(cordonnier)-0.10.doc MTOM Provide and Register]. Tech Editor: Roberto Ruggeri (Vassil at Dec 5th meeting)
4. [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Planning_Cmte/Detailed%20Profile%20Proposals/IHE-Policy%20and%20Config%20Doc%20Sharing-Detailed%20Profile%20Proposal.doc Policy and Configuration Document Sharing (XDS for non-patient-centric data)] : Tech Editor: Charles Parisot
5. [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Planning_Cmte/Detailed%20Profile%20Proposals/IHE_Profile_Proposal_WebServicesInfrastructure-11-30-06.doc Web Services Infrastructure for HL7 V3 (for PCC Support for EMR Query and ATNA as well PIX/PDQ V3 Query)] : Tech Editor : Vassil Peytchev – To be confirmed
'''Technical/Planning Committee to clarify requirements'''
6. [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Planning_Cmte/Detailed%20Profile%20Proposals/IHE%20ITI%20Aggregate%20Data-V2.doc 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. Tech Editor: Floyd Eisenberg
'''Technical Committee White Paper'''
7. [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Planning_Cmte/Detailed%20Profile%20Proposals/IHE_whitepaper_Proposal_ConfigMgt02.doc Overall Configuration Management White Paper (Incl HL7, DICOM, etc.)]. For ITI TC development in 2007. Tech Editor: Rob Horn
'''Planning Committee White Papers'''
8. [ftp://ftp.ihe.net/IT_Infrastructure/iheitiyr5-2007-2008/Planning_Cmte/Detailed%20Profile%20Proposals/Implementing%20The%20Markle%20Patient%20and%20Consumer%20Principles%20for%20System%20Design%2020061003.doc Implementing The Markle Patient and Consumer Principles For System Design]. Tech Editor: John Moehrke
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.
==Demonstrations & Presentations==
These items were '''selected''' by the Planning Committee for this Cycle:
Presentations are all presented on [https://www.youtube.com/@IHEIntl/videos YouTube in IHE-International]
* To be published in January 2007
==Demonstrations & Presentations==
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]
* [[ITI,_PCC_%26_QRPH_Meetings|ITI, PCC & QRPH Development Cycle Meetings]]
[[ITI Vocabulary Registry and Data Dictionary]]
* [[Committees]]
*This page is based on the [[Domain Template]].
[[category: IT Infrastructure]]
This page is based on the [[Domain Template]].
[[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.
