CP IHE Document Sharing: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
starter requirements list
Sauermann (talk | contribs)
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Disclaimer / Document Status==
== Disclaimer / Document Status==
This is a preliminary draft. The intention is to understand how this "extended" / "advanced" profile relates to the basic CP IHE Foundation profile.  
This is a preliminary draft. The intention of this "IHE Certified Professional Document Sharing" (ICP Document Sharing) skill profile is to understand how this "extended" / "advanced" profile relates to the basic [[CP IHE Foundation|ICP Foundation]] profile.  
This is very early. More work needed!!
This is an early workgroup draft. More work needed!!
 


== Business Outcomes ==
== Business Outcomes ==
The business outcomes describe how a CP IHE Document Sharing typically contributes to activities in the healthcare enterprise
The business outcomes describe how a ICP Document Sharing typically contributes to activities in the healthcare enterprise.


A competent CP IHE Document Sharing will:
The key concepts that an ICP Document Sharing needs to know are outlined in the IHE White Paper [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_White-Paper_Enabling-doc-sharing-through-IHE-Profiles_Rev1-0_2012-01-24.pdf "Health Information Exchange: Enabling Document Sharing Using IHE Profiles"].


* take a leading role in software implementation teams
'''Target audience/prerequisite skills''' for a ICP Document Sharing: 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. Such person is involved in a health information community of any size that plans to use or uses IHE profiles to address interoperability aspects of common document sharing problems.
* ...


== Learning Outcomes ==
A competent ICP Document Sharing will be able to apply the IHE methodology (ISO/TR 28380) to an existing healthcare environment, and will have the skills to identify and use the appropriate IHE profiles when faced with document sharing problems in a healthcare interoperability project, as in the CP IHE Foundation. They will additionally be familiar with transaction details and can use this knowledge to support developers in implementing IHE document sharing profiles.
The following levels of learning outcomes are used, in the order of complexity:
* reproduce and explain
* apply and implement
* analyse and develop


A competent CP IHE Document Sharing should be able to:
At a more detailed level, a competent ICP Document Sharing will be able to (note: the XDS-family of profiles shall be denoted by "XD*")


=== software development experience ===
* provide training and support developer teams during implementation of the IHE Document Sharing Profiles including details and variants of transactions as they are necessary for specific settings:
* develop software, having sufficient experience in implementation projects
** Document exchange: XDS, XDR, XDM, XCA,
* ...
** Identity management: PIX, PDQ, XCPD, MPQ
** Security: ATNA, CT, BPPC, XUA
** Codelists and value sets: SVS


* capture the interoperability requirements of users in healthcare and formulate specifications using Document Sharing profiles


A competent CP IHE Document Sharing xxxxxxxxxxxxxxx
* adress interoperability issues that arise during implementation and answer them using IHE resources and contacts


* follow the continuous extension and development of Document Sharing within IHE securing long term investments


At a more detailed level, a competent CP IHE Document Sharing will be able to (note: the XDS-family of profiles shall be denoted by "XDS*")
* negotiate specific issues of IHE Document Sharing conformance e.g during procurement, development or maintenance


* provide training and introduce teams into the concepts of IHE and XDS*
* map user and system requirements to IHE Document Sharing profiles throughout the software life cycle


* assess the available IHE related skills within a team, identify gaps, provide guidance on how missing knowledge can be acquired
* together with legal and administrative experts conceptualise how specific regulatory requirements can be addressed using IHE security and privacy profiles
* identify components in existing IT systems that conform to XDS* profiles
* conceptualise IHE XDS* based extensions of existing IT systems
* support teams to identify and understand the base standards that are necessary to implement IT systems based on XDS*
* capture the interoperability requirements of users in healthcare and formulate specifications using XDS* profiles


* plan, manage and perform pre-Connectathon and Connectathon testing of XDS* based IT systems
* support teams in selecting and applying document sharing content profiles of the Patient Care Coordination Technical Framework for specific requirements
* adress interoperability issues that arise during implementation and answer them using IHE resources and contacts
 
== Learning Outcomes ==
The following levels of learning outcomes are used, in the order of complexity:
* reproduce and explain
* apply and implement
* analyse and develop


* follow the continuous extension and development of XDS* within IHE securing long term investments
A competent ICP Document Sharing should be able to:
* contribute to IHE XDS* profile development, representing the requirements of the institution


* perform a market analysis of products and vendors regarding conformance to XDS* profiles
* List the profiles included in IHE Document Sharing
* negotiate specific issues of IHE XDS* conformance e.g during procurement, development or maintenance
* Understand and explain the value of this grouping of profiles
* map user and system requirements to IHE XDS* profiles throughout the software life cycle
* Understand and explain the commonalities across all the profiles included in Document Sharing
* Understand and explain the distinctions between the different Document Sharing profiles and which environment each is best designed to support
* Explain the purpose and value of each of the metadata attributes used for Document Sharing
* Explain document relationships
* Understand and explain the supporting profiles which enable foundational aspects of Document Sharing
* Be able to apply Security and Privacy principles to Document Sharing environments


* together with legal and administrative experts conceptualise how specific regulatory requirements can be addressed using IHE security and privacy profiles
=== software development experience ===
* develop software, having sufficient experience in implementation projects
* ...


== Related Groups ==
== Related Groups ==

Latest revision as of 15:02, 31 March 2015

Disclaimer / Document Status

This is a preliminary draft. The intention of this "IHE Certified Professional Document Sharing" (ICP Document Sharing) skill profile is to understand how this "extended" / "advanced" profile relates to the basic ICP Foundation profile. This is an early workgroup draft. More work needed!!

Business Outcomes

The business outcomes describe how a ICP Document Sharing typically contributes to activities in the healthcare enterprise.

The key concepts that an ICP Document Sharing needs to know are outlined in the IHE White Paper "Health Information Exchange: Enabling Document Sharing Using IHE Profiles".

Target audience/prerequisite skills for a ICP Document Sharing: 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. Such person is involved in a health information community of any size that plans to use or uses IHE profiles to address interoperability aspects of common document sharing problems.

A competent ICP Document Sharing will be able to apply the IHE methodology (ISO/TR 28380) to an existing healthcare environment, and will have the skills to identify and use the appropriate IHE profiles when faced with document sharing problems in a healthcare interoperability project, as in the CP IHE Foundation. They will additionally be familiar with transaction details and can use this knowledge to support developers in implementing IHE document sharing profiles.

At a more detailed level, a competent ICP Document Sharing will be able to (note: the XDS-family of profiles shall be denoted by "XD*")

  • provide training and support developer teams during implementation of the IHE Document Sharing Profiles including details and variants of transactions as they are necessary for specific settings:
    • Document exchange: XDS, XDR, XDM, XCA,
    • Identity management: PIX, PDQ, XCPD, MPQ
    • Security: ATNA, CT, BPPC, XUA
    • Codelists and value sets: SVS
  • capture the interoperability requirements of users in healthcare and formulate specifications using Document Sharing profiles
  • adress interoperability issues that arise during implementation and answer them using IHE resources and contacts
  • follow the continuous extension and development of Document Sharing within IHE securing long term investments
  • negotiate specific issues of IHE Document Sharing conformance e.g during procurement, development or maintenance
  • map user and system requirements to IHE Document Sharing 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
  • support teams in selecting and applying document sharing content profiles of the Patient Care Coordination Technical Framework for specific requirements

Learning Outcomes

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

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

A competent ICP Document Sharing should be able to:

  • List the profiles included in IHE Document Sharing
  • Understand and explain the value of this grouping of profiles
  • Understand and explain the commonalities across all the profiles included in Document Sharing
  • Understand and explain the distinctions between the different Document Sharing profiles and which environment each is best designed to support
  • Explain the purpose and value of each of the metadata attributes used for Document Sharing
  • Explain document relationships
  • Understand and explain the supporting profiles which enable foundational aspects of Document Sharing
  • Be able to apply Security and Privacy principles to Document Sharing environments

software development experience

  • develop software, having sufficient experience in implementation projects
  • ...

Related Groups

Education_Workgroup

Global Deployment Coordination Committee