CP IHE Document Sharing: Difference between revisions
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
|||
| Line 32: | Line 32: | ||
A competent CP IHE Document Sharing should be able to: | A competent CP IHE 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 | |||
* Understand and explain the critical supporting profiles which enable foundational aspects of Document Sharing | |||
=== software development experience === | === software development experience === | ||
* develop software, having sufficient experience in implementation projects | * develop software, having sufficient experience in implementation projects | ||
* ... | * ... | ||
== Related Groups == | == Related Groups == | ||
Revision as of 12:26, 20 February 2015
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.
Target audience/prerequisite skills for a CP IHE Document Sharing: xxxxxxxxxxxxx
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 and implementation details of IHE XDS*
- capture the interoperability requirements of users in healthcare and formulate specifications using XDS* profiles
- 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
- 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
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:
- 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
- Understand and explain the critical supporting profiles which enable foundational aspects of Document Sharing
software development experience
- develop software, having sufficient experience in implementation projects
- ...