From IHE Wiki
Revision as of 10:36, 23 August 2007 by Kboone (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Development Only

The PCC Wiki Content is used only for development of IHE PCC Content. The Normative content of the PCC Technical Framework and the current supplements can be found at http://www.ihe.net/Technical_Framework/index.cfm#PCC

Trial.gif PHR Update Specification

The PHR Update Content Module is similar to the PHR Extract content module, except that it has a number of different constraints. First of all, it is not required to contain all of the information that the PHR Extract content module does. The reason for this is because the purpose of this module is to reflect the changes that should be made to a PHR based on a previously existing PHR Extract content module. So, while it makes use of the same data element index, almost all of the data elements are optional. The purpose of this module is to make it easier for an EHR to create content that can be used to update a PHR.

Format Code

The XDSDocumentEntry format code for this content is urn:ihe:pcc:xphr:2007


CDA Release 2.0 documents that conform to the requirements of this content module shall indicate their conformance by the inclusion of the appropriate <templateId> elements in the header of the document. This is shown in the sample document below.

Sample PHR Update Document
<ClinicalDocument xmlns='urn:hl7-org:v3'>
  <typeId extension="POCD_HD000040" root="2.16.840.1.113883.1.3"/>
  <templateId root=''/>
  <id root=' ' extension=' '/>
  <code code=' ' displayName=' '
    codeSystem='2.16.840.1.113883.6.1' codeSystemName='LOINC'/>
  <title>PHR Update</title>
  <effectiveTime value='20230329012005'/>
  <confidentialityCode code='N' displayName='Normal' 
    codeSystem='2.16.840.1.113883.5.25' codeSystemName='Confidentiality' />
  <languageCode code='en-US'/>     


   <!-- Verify the document type code -->
   <assert test='cda:code[@code = "{{{LOINC}}}"]'>
     Error: The document type code of a PHR Update must be {{{LOINC}}}
   <assert test='cda:code[@codeSystem = "2.16.840.1.113883.6.1"]'>
     Error: The document type code must come from the LOINC code 
     system (2.16.840.1.113883.6.1).

The requirements of this module are that it support recording updates to the original PHR Extract. The PHR Extract is made up of a header, and several sections, each of which may contain one or more entries. Suggestions to add, remove or update a section or entry are described in more detail below.

Adding a New Section or Appending to an Existing Section

A PHR Reviewer Actor may suggest additional material for an existing or new section by simply adding that section to the PHR Update document.

Replacing a Section

A PHR Reviewer Actor may suggest a revision to a section in the PHR Extract by replacing that section. To replace a section, the PHR Reviewer Actor creates a section in the PHR Update document that is of the same type as the section to be replaced in the PHR Extract document, and adds a <ppc:replacementOf> element to that section to indicate the section that it replaces.

The replacementOf element is an extension to the CDA Release 2.0 standard, and is further described below in Appendix C Extensions to CDA Release 2.0.

Adding an Entry

A PHR Reviewer Actor may suggest a new entry be added to a section by simply including that entry in a like section in the PHR Update document.

Replacing or Removing an Entry

The PHR Review Actor can replace an existing entry by adding an entry of the same type with new or modified information, and including in that entry a <reference> element that has an <externalAct> element. The <id> element of the <externalAct> shall be that of the act that is being replaced

Removing an Entry

The PHR Reviewer Actor can suggest that an entry be removed by replacing it with an act who <statusCode> element has been set to nullified.


The LOINC document type code is the same as for the PHR Extract content module. The PHR Update Content module must record the PHR Extract which it is updating