CP IHE Foundation: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older edit
Kevino (talk | contribs)
editor
4,951 edits
Sauermann (talk | contribs)
526 edits
 
(23 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Disclaimer / Document Status==
== Introductionary remarks / Document Status ==
This is a preliminary draft. The intention is to provide a "beginner" "general purpose" profile that a large number of individuals may acquire. This profile may then be extended into e.g the [[CP IHE Document Sharing]]. We first need to understand the idea of CPs and how modular CP profiles may address the user needs.
This is a workgroup draft that already had some review cycles. The intention of this "Certified Professional IHE Foundation Level" (ICP Foundation Level) skills profile is to provide a "beginner" "general purpose" profile that a large number of individuals may acquire. The intent is for the certification testing to be closed book using an online testing process.  


== Business Outcomes ==
The business outcomes describe how a CP IHE Foundation typically contributes to activities in the healthcare enterprise


'''Target audience/prerequisite skills''' for a CP IHE Foundation: xxxxxxxxxxxxx
This profile may then be extended upon e.g the [[CP IHE Document Sharing| ICP Document Sharing]]. These will likely be tested open book exams and assessment of prior knowledge and experience.


*Discussion: suggest to add a 1-paragraph management summary of the list below. The list is too detailed to be used in e.g. a marketing statement. [[User:Rene spronk|Rene spronk]] 06:51, 26 January 2015 (CST)
We first need to understand the idea of ICPs and how modular ICP profiles may address the user needs.


A competent CP IHE Foundation xxxxxxxxxxxxxxx
== Business Outcomes ==
 
The business outcomes describe how a ICP Foundation typically contributes to activities in the healthcare enterprise
 
At a more detailed level, a competent CP IHE Foundation will be able to:
 
* provide training and introduce teams into the concepts of IHE
 
* assess the available IHE related skills within a team, identify gaps, provide guidance on how missing knowledge can be acquired
* identify components in existing IT systems that conform to IHE profiles
* conceptualise IHE based extensions of existing IT systems
* support teams to identify and understand the base standards that are necessary to implement IT systems based on IHE
* capture the interoperability requirements of users in healthcare and formulate specifications using IHE profiles
 
* plan, manage and perform pre-Connectathon and Connectathon testing of IT systems
* adress interoperability issues that arise during implementation and answer them using IHE resources and contacts
 
* follow the continuous extension and development of TFs within IHE securing long term investments
* contribute to IHE profile development, representing the requirements of the institution


* perform a market analysis of products and vendors regarding conformance to IHE profiles
'''Target audience/prerequisite skills''' for a ICP Foundation: a person with a health IT background with a requirement to use IHEs products, either someone (contracted) to work for a healthcare provider organization, or someone employed by a software development company.
* negotiate specific issues of IHE conformance e.g during procurement, development or maintenance
* map user and system requirements to IHE profiles throughout the software life cycle


* together with legal and administrative experts conceptualise how specific regulatory requirements can be addressed using IHE security and privacy profiles
A competent ICP Foundation will be able to apply the IHE methodology (ISO/TR 28380) to develop interoperability specifications for an existing healthcare environment, and will have the skills to identify and use the appropriate existing IHE profiles when faced with a healthcare interoperability project.


At a more detailed level, a competent ICP Foundation will be able to:


*'''Discussion'''
#IHE Methodology
**This list includes requirements for 'IHE profile users' as well as 'IHE profile developers' (the second group will be much smaller than the first). Knowledge of the profile creation/amendment process will be useful, but to me the capabilities related to 'using IHE profiles' should be a priority. [[User:Rene spronk|Rene spronk]] 06:48, 26 January 2015 (CST)
#* explain the concepts and organisational structure of IHE to teams
**We should be careful to let these criteria be a blend between a) what a CP would need to know when using IHE profiles in a provider organization (whilst working for that organization), and b) what a CP would need when working for a software vendor, and implementing some of the profiles/actors in a software application. Both target audiences should be served. [[User:Rene spronk|Rene spronk]] 06:48, 26 January 2015 (CST)
#** explain the process of the Connectathon
*The requirements above - how are they to be tested? If we can't do that in a SMART way the requirement itself may have to rephrased. If we can only test a requirement by doing an "interview" then it's probably not a good requirement - we don't have the time nor the money to set up such a costly interviewing scheme. [[User:Rene spronk|Rene spronk]] 02:43, 27 January 2015 (CST)
#** contribute to IHE profile development by submitting "Change Proposals", e.g. if new requirements arise, or if they find an issue in an existing profile
#* capture the interoperability requirements of users in healthcare and formulate specifications using the IHE profile development methodology (ISO/TR 28380).  
#** identify components in existing IT systems that conform to IHE profiles
# IHE Technical Frameworks and Profiles
#* capture the interoperability requirements of users in healthcare and formulate specifications using existing IHE profiles.  
#** conceptualise the use of additional IHE profiles, in existing IT systems, in order to support additional workflows.
#** explain and identify upcoming IHE profiles that are still in development
#** together with legal and administrative experts conceptualise how specific regulatory requirements can be addressed using existing IHE security and privacy profiles
#* assess the available IHE and base standard related skills within a team, identify gaps, provide guidance on how missing knowledge can be acquired
#* help resolve specific issues of IHE conformance e.g during procurement, development or maintenance
#** capture interoperability issues that arise during implementation and help to answer them using IHE resources and contacts
#** perform a market analysis of products and vendors regarding conformance to IHE profiles using the IHE Connectathon results database


== Learning Outcomes ==
== Learning Outcomes ==
Line 46: Line 38:
* analyse and develop
* analyse and develop


A competent CP IHE Foundation should be able to:
All of these learning outcomes will be tested as part of the certification process.
 
=== IHE Basics ===
* understand the main concepts of IHE (actors, transactions,...), the document structure of IHE technical frameworks.
* understand the structure and processes of IHE especially for developing the technical frameworks
* understand the structure and processes of IHE for testing at the Connectathon
* understand and generate integration statements
* explain the IHE domains
* research information from IHE sources: IHE homepage, Wiki, FTP
 
=== Procurement, Management ===
* conduct simple and advanced browsing in the CAT results matrix and product registry
*
 
*Comment: [[User:Rene spronk|Rene spronk]] 02:40, 27 January 2015 (CST) I woudn't group things on a per-TF basis.
*#We probably want 'application / analitical' skills when it comes to the top 20 profiles (see [http://www.ringholm.com/column/usage_of_IHE_profiles.htm http://www.ringholm.com/column/usage_of_IHE_profiles.htm], this is easy to determine in an objective way), and
*#'reproduction / explain' skills for a selection of second-tier profiles (that are not used that often, or where we expect high future usage). This is a subjective selection, which may lead to problems from a global perspective, som ptofiles are more heavily used in some areas than others.
*#Of a third-tier of profiles we can only expect that they've 'heard of the profile' and know how to find it and apply it if necessary.
*#Besides that we have general prerequisite knowledge of XML/WS-*/Security etc. which will need to be identified.
 
=== IT Infrastructure ===
* provide an overview of the main IT Infrastructure TF profiles
* understand and explain the XDS profile including the concept of XDS metadata
* explain the difference between XDR, XDM and XDS profiles and their interrelation
* explain the IHE Cross-Community profiles XCA, XCPD
* explain the concepts of Identity Management in IHE in the PIX and PDQ profiles
* explain the concept of a Healthcare Provider Directory
* understand and explain the relation between IHE IT TF and real world EHR architectures
* understand and explain the concepts of the Cross-Enterprise Document Workflow (XDW) profile
* understand and explain the basic concepts of IT TF base standards: HL7 V3, CDA, HL7V2.X, OASIS
* understand and explain the nomenclatures and coding systems used in IHE IT TF: LOINC, SnomedCT, ICD, HL7 codes
 
 
=== Security, Privacy ===
* understand and explain the basics of IT-Security : CIA-Triad, Encryption, digital signatures, certificates, Authorization Models, Policies, federated identity management
* explain the base standards and technologies and as they are used in the IHE Security Profiles: SAML, WS-Trust, XACML
* understand and explain the IHE profiles CT, ATNA, XUA, BPPC
 
 
=== Radiology ===
* understand and explain the IHE Radiology Scheduled Workflow (SWF) profile
* provide an overview of the Radiology TF
* understand and explain the use of XDS-I for sharing images


A competent ICP Foundation should be able to:


=== Laboratory ===
#IHE Methodology
* provide an overview of the Laboratory Testing Workflow (LTW), Laboratory Device Automation (LDA), and Laboratory Analytical Workflow (LAW) profiles
#* understand the main concepts of IHE (actors, transactions,...), the document structure of IHE technical frameworks.
#* understand the structure and processes of IHE especially for developing the technical frameworks
#* understand the structure and processes of IHE for testing at the Connectathon
#* understand and generate integration statements
#* explain the IHE domains
#* research information from IHE sources: IHE homepage, Wiki, FTP
#* conduct simple and advanced browsing in the CAT results matrix and product registry
#IHE Example profiles, base standards, general healthcare IT knowledge
#* understand and explain base standards such as XML
#* understand and explain the basic concepts of IHE base standards: HL7 V3, CDA, HL7V2.X, OASIS
#* understand and explain the basic concepts of terminologies, ontologies, coding systems and value sets used in the IHE, specifically LOINC, SnomedCT, ICD and HL7 tables.
#* understand and explain the basics of Security : CIA-Triad, encryption, digital signatures, certificates, authorization models, policies, federated identity management.
#* understand an apply the 'top 20 most often implemented profiles' (as determined by looking at CAT statistics)
#** A draft list of ranked profiles is available [ftp://ftp.ihe.net/GDC/EducationWG/ICPFoundation_2016/D_IHECATResults_2010To2015_TestedProfiles_V00.01.xlsx here]
#** Go [http://wiki.ihe.net/index.php?title=EduWG_Minutes_2015-04-13#Review_of_ICP_drafts here] for how this list was created and ranked
#* be aware of the existence and scope of all other profiles


== Related Groups ==
== Related Groups ==
Line 100: Line 66:
[[Global Deployment Coordination Committee]]
[[Global Deployment Coordination Committee]]


[http://siim.org/?page=iip_ciip_career SIIM Certified Imaging Informatics Professional] - IHE Radiology has contacts IHE can consult with
[http://siim.org/?page=iip_ciip_career SIIM Certified Imaging Informatics Professional] - IHE Radiology has contacts IHE can consult with about their program


[[Category: Minutes]]
[[Category: Minutes]]

Latest revision as of 08:08, 7 January 2016

Introductionary remarks / Document Status

This is a workgroup draft that already had some review cycles. The intention of this "Certified Professional IHE Foundation Level" (ICP Foundation Level) skills profile is to provide a "beginner" "general purpose" profile that a large number of individuals may acquire. The intent is for the certification testing to be closed book using an online testing process.


This profile may then be extended upon e.g the ICP Document Sharing. These will likely be tested open book exams and assessment of prior knowledge and experience.

We first need to understand the idea of ICPs and how modular ICP profiles may address the user needs.

Business Outcomes

The business outcomes describe how a ICP Foundation typically contributes to activities in the healthcare enterprise

Target audience/prerequisite skills for a ICP Foundation: a person with a health IT background with a requirement to use IHEs products, either someone (contracted) to work for a healthcare provider organization, or someone employed by a software development company.

A competent ICP Foundation will be able to apply the IHE methodology (ISO/TR 28380) to develop interoperability specifications for an existing healthcare environment, and will have the skills to identify and use the appropriate existing IHE profiles when faced with a healthcare interoperability project.

At a more detailed level, a competent ICP Foundation will be able to:

  1. IHE Methodology
    • explain the concepts and organisational structure of IHE to teams
      • explain the process of the Connectathon
      • contribute to IHE profile development by submitting "Change Proposals", e.g. if new requirements arise, or if they find an issue in an existing profile
    • capture the interoperability requirements of users in healthcare and formulate specifications using the IHE profile development methodology (ISO/TR 28380).
      • identify components in existing IT systems that conform to IHE profiles
  2. IHE Technical Frameworks and Profiles
    • capture the interoperability requirements of users in healthcare and formulate specifications using existing IHE profiles.
      • conceptualise the use of additional IHE profiles, in existing IT systems, in order to support additional workflows.
      • explain and identify upcoming IHE profiles that are still in development
      • together with legal and administrative experts conceptualise how specific regulatory requirements can be addressed using existing IHE security and privacy profiles
    • assess the available IHE and base standard related skills within a team, identify gaps, provide guidance on how missing knowledge can be acquired
    • help resolve specific issues of IHE conformance e.g during procurement, development or maintenance
      • capture interoperability issues that arise during implementation and help to answer them using IHE resources and contacts
      • perform a market analysis of products and vendors regarding conformance to IHE profiles using the IHE Connectathon results database

Learning Outcomes

The following levels of learning outcomes are used, in the order of complexity:

  • reproduce and explain
  • apply and implement
  • analyse and develop

All of these learning outcomes will be tested as part of the certification process.

A competent ICP Foundation should be able to:

  1. IHE Methodology
    • understand the main concepts of IHE (actors, transactions,...), the document structure of IHE technical frameworks.
    • understand the structure and processes of IHE especially for developing the technical frameworks
    • understand the structure and processes of IHE for testing at the Connectathon
    • understand and generate integration statements
    • explain the IHE domains
    • research information from IHE sources: IHE homepage, Wiki, FTP
    • conduct simple and advanced browsing in the CAT results matrix and product registry
  2. IHE Example profiles, base standards, general healthcare IT knowledge
    • understand and explain base standards such as XML
    • understand and explain the basic concepts of IHE base standards: HL7 V3, CDA, HL7V2.X, OASIS
    • understand and explain the basic concepts of terminologies, ontologies, coding systems and value sets used in the IHE, specifically LOINC, SnomedCT, ICD and HL7 tables.
    • understand and explain the basics of Security : CIA-Triad, encryption, digital signatures, certificates, authorization models, policies, federated identity management.
    • understand an apply the 'top 20 most often implemented profiles' (as determined by looking at CAT statistics)
      • A draft list of ranked profiles is available here
      • Go here for how this list was created and ranked
    • be aware of the existence and scope of all other profiles

Related Groups

Education_Workgroup

Global Deployment Coordination Committee

SIIM Certified Imaging Informatics Professional - IHE Radiology has contacts IHE can consult with about their program

Retrieved from "http://wiki.ihe.net/index.php?title=CP_IHE_Foundation&oldid=91691"