CP IHE Document Sharing

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 very early. More work needed!!

Business Outcomes

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

A competent CP IHE Document Sharing will:

• take a leading role in software implementation teams
• ...

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 CP IHE Document Sharing should be able to:

software development experience

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

A competent CP IHE Document Sharing xxxxxxxxxxxxxxx

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*")

• provide training and introduce teams into the concepts of IHE and XDS*

• 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 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
• adress interoperability issues that arise during implementation and answer them using IHE resources and contacts

• follow the continuous extension and development of XDS* within IHE securing long term investments
• 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
• negotiate specific issues of IHE XDS* conformance e.g during procurement, development or maintenance
• map user and system requirements to IHE XDS* 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

Related Groups

Education_Workgroup

Global Deployment Coordination Committee