cdaefa:ECR Participating Healthcare Providers Content Module - Versionsgeschichte

Jcaumanns: /* Example */

2012-03-18T16:19:07Z

‎Example

Jcaumanns: /* Example */

2012-03-18T16:18:46Z

‎Example

Jcaumanns: /* Template */

2012-03-18T16:17:31Z

‎Template

Jcaumanns: /* Template */

2012-03-18T10:19:10Z

‎Template

Jcaumanns: /* Template */

2012-03-18T10:18:09Z

‎Template

Jcaumanns: /* Template */

2012-03-18T10:17:40Z

‎Template

Jcaumanns: /* Logical View */

2012-03-18T10:16:13Z

‎Logical View

Jcaumanns: /* Standards */

2012-03-17T21:42:00Z

‎Standards

Jcaumanns: /* Template */

2012-03-17T21:41:00Z

‎Template

Jcaumanns am 17. März 2012 um 21:19 Uhr

2012-03-17T21:19:12Z

@@ Zeile 66: / Zeile 66: @@
              <templateId root='1.3.6.1.4.1.19376.1.5.3.1.2.3'/>
-<!—Dr. Musterarzt is registered as the operative case manager -->
+<!-- Dr. Musterarzt is registered as the operative case manager -->
              <functionCode code='OPCMGR' displayName='Case Manager'
                 codeSystem='1.2.276.0.76.3.1.81.81.5.2'

@@ Zeile 59: / Zeile 59: @@
 == Example ==
-<pre>
+<syntaxhighlight lang="xml">
     <documentationOf>
        <serviceEvent classCode="PCPR">
@@ Zeile 81: / Zeile 81: @@
                 <telecom value='tel:+49(30)234-5678'/>
                 <assignedPerson>
-                   <name>Dr. John Musterarzt</name>
+                   <name><given>John</given><family>Musterarzt</family></name>
                 </assignedPerson>
                 <representedOrganization>
@@ Zeile 103: / Zeile 103: @@
        </serviceEvent>
     </documentationOf>
-</pre>
+</syntaxhighlight>

@@ Zeile 17: / Zeile 17: @@
 == Template ==
-<code>
+<syntaxhighlight lang="xml" heading="template - ECR Participating Healthcare Provider" valid="true" highlight="7-17">
     <documentationOf>
        <serviceEvent classCode="PCPR">
           <effectiveTime value="..."/>
           <performer typeCode="PRF">
-             <templateId root='1.3.6.1.4.1.19376.1.5.3.1.2.3'/></code><code style="color:red;">
+             <templateId root='1.3.6.1.4.1.19376.1.5.3.1.2.3'/>
              <!-- eCR Role Code (other services MAY use different role codes -->
              <functionCode code='' displayName=''
@@ Zeile 30: / Zeile 30: @@
              <assignedEntity>
                 <templateId root='1.2.276.0.76.3.1.81.81.6.2.2|3'/>
-                <id root= extension= /></code><code>
+                <id root= extension= />
-                ...</code><code style="text-decoration:line-through;">
+                ...
                 <sdtc:patient>
                    <sdtc:id root= extension= />
-                </sdtc:patient></code><code>
+                </sdtc:patient>
              </assignedEntity>
           </performer>
        </serviceEvent>
     <documentationOf>
-</code>
+</syntaxhighlight>
 ;<effectivetime value=' ...'/>
 :This element records the date when the setup of the care team was last modified.
 ;<functionCode code= displayName=
-;:    codeSystem='1.2.276.0.76.3.1.81.81.5.2' codeSystemName='eCR Participant Function Code'/>
+;<functionCode code= displayName= <br>&nbsp;&nbsp;&nbsp;codeSystem='1.2.276.0.76.3.1.81.81.5.2' codeSystemName='eCR Participant Function Code'/>
 :This element defines the functional role of a healthcare provider (organization) within the documented clinical setting. Roles MUST be encoded using a code system with clearly defined semantics and responsibilities of the different functional roles.
 :An example for such a code system is the [[cdaefa:1.2.276.0.76.3.1.81.81.5.2|eCR Participant Function (1.2.276.0.76.3.1.81.81.5.2)]] code system.
 ;<time><low value=' '/><high value=' '/></time>
 :This element MUST record the validity timespan of the authorization. The maximum validity time of a consent/authorization MUST be defined depending on the diagnosis and the contractual setting.
 ;<assignedEntity>
-;:    <templateId root='1.2.276.0.76.3.1.81.81.6.2.2|3'/>
+;<assignedEntity><br>&nbsp;&nbsp;&nbsp;<templateId root='1.2.276.0.76.3.1.81.81.6.2.2|3'/>
 :This entry MUST comply with the Assigned Human Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.2|1.2.276.0.76.3.1.81.81.6.2.2]]) as defined in this document or with the Assigned Organizational Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.6|1.2.276.0.76.3.1.81.81.6.2.6]]) as defined in this document.
 ;<sdtc&#58;patient>
-;:    <sdtc&#58;id root= extension= />
+;<sdtc&#58;patient><br>&nbsp;&nbsp;&nbsp;<sdtc&#58;id root= extension= />
 :This element is optional for the underlying IHE PCC content module and SHOULD NOT be used unless there is a clear reason for disclosing local patient identifers. If used, it MUST hold the organization’s local identifier of the patient who is identified in the <patientRole> entry.

@@ Zeile 51: / Zeile 51: @@
 ;<assignedEntity>
 ;:    <templateId root='1.2.276.0.76.3.1.81.81.6.2.2|3'/>
-:This entry MUST comply with the Assigned Human Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.2|1.2.276.0.76.3.1.81.81.6.2.2]]) as defined in this document or with the Assigned Organizational Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.3|1.2.276.0.76.3.1.81.81.6.2.3]]) as defined in this document.
+:This entry MUST comply with the Assigned Human Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.2|1.2.276.0.76.3.1.81.81.6.2.2]]) as defined in this document or with the Assigned Organizational Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.6|1.2.276.0.76.3.1.81.81.6.2.6]]) as defined in this document.
 ;<sdtc&#58;patient>
 ;:    <sdtc&#58;id root= extension= />

@@ Zeile 51: / Zeile 51: @@
 ;<assignedEntity>
 ;:    <templateId root='1.2.276.0.76.3.1.81.81.6.2.2|3'/>
-:This entry MUST comply with the Assigned Human Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.2|1.2.276.0.76.3.1.81.81.6.2.2]]) as defined in this document or with the Assigned Organizational Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.3|1.2.276.0.76.3.1.81.81.6.2.3) as defined in this document.
+:This entry MUST comply with the Assigned Human Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.2|1.2.276.0.76.3.1.81.81.6.2.2]]) as defined in this document or with the Assigned Organizational Entity Content Module ([[cdaefa:1.2.276.0.76.3.1.81.81.6.2.3|1.2.276.0.76.3.1.81.81.6.2.3]]) as defined in this document.
 ;<sdtc&#58;patient>
 ;:    <sdtc&#58;id root= extension= />

@@ Zeile 4: / Zeile 4: @@
 == Logical View ==
-This specification follows the IHE 5-Domain-Modell (see IHE White Paper on “Access Control”) and separates between the static structural role a user has within a certain medical facility (subject domain) and his/her functional role within the current context (context domain). Per-missions are solely bound to functional roles. This allows for a coarse grainded assignment of roles and a fine grained enforcement of permissions (simplicity and flexibility):
+This specification follows the IHE 5-Domain-Modell (see [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_WhitePaper_AccessControl_2009-09-28.pdf IHE White Paper on “Access Control”]) and separates between the static structural role a user has within a certain medical facility (subject domain) and his/her functional role within the current context (context domain). Permissions are solely bound to functional roles. This allows for a coarse grainded assignment of roles and a fine grained enforcement of permissions (simplicity and flexibility):
 * Functional roles are defined based on a specific application semantics (e.g. electronic CaseRecord or Booking System). A functional role integrates typical working tasks of the application which are usually performed by a single person (see HL7 role engineering for how to analyse functional roles). Functional roles may be medical roles (e.g. “treating physician”) or administraive roles (e.g. “privacy commissionar”).
-* Permissions are bound to functional roles and reflect the rights on data and services a holder of that role requires to perform his/her assigned tasks. A functional role’s permis-sions are encoded as a policy (which MAY even be implizit; e.g. as in IHE BPPC).
+* Permissions are bound to functional roles and reflect the rights on data and services a holder of that role requires to perform his/her assigned tasks. A functional role’s permissions are encoded as a policy (which MAY even be implizit; e.g. as in [http://wiki.ihe.net/index.php?title=Basic_Patient_Privacy_Consents IHE BPPC]).
 * During authorization concrete persons/organizations instantiate the functional roles for a certain (instance of an) application (e.g. Dr. Schmidt taking the role of a case manager for a certain case record instance).
 * When a user tries to perform a protected operation the policy that is assigned to his/her assigned functional role is assessed and enforced.

@@ Zeile 13: / Zeile 13: @@
 == Standards ==
-* IHE PCC Healthcare Providers and Pharmacies (1.3.6.1.4.1.19376.1.5.3.1.2.3)
+* [http://wiki.ihe.net/index.php?title=1.3.6.1.4.1.19376.1.5.3.1.2.3 IHE PCC Healthcare Providers and Pharmacies (1.3.6.1.4.1.19376.1.5.3.1.2.3)]
 == Template ==