My favorites | English | Sign in

Faster apps faster - GWT 2.0 with Speed Tracer New!

Google Health Data API

Google Health Data API CCR Reference

Google supports a subset of the Continuity of Care (CCR) standard. This "CCR Reference" documents only those aspects of the CCR standard that Google supports.

A CCR entry has three components: a "Header," a "Footer" and one component that is the <Body> element.

The first two sections of this document describe the Header and the Footer. The third section contains an alphabetical reference for all the remaining supported CCR elements, including <Body>.

  1. Header
  2. Footer
  3. CCR Reference

Mapping CCR Elements to the Google Health UI

For information on how specific CCR elements map to the Google Health UI, see each section under Mapping CCR Elements to the Google Health UI:

Below is the tree diagram for supported CCR elements. In this diagram, elements to the right on a particular branch in the tree are extensions of the elements to their left.

Note: Click on an element name in this diagram to jump to its entry in the reference section.



Header

The Header identifies the format of the record, and the time it was created. The Header consists of the CCR XML Document Header and the following elements:

CCR XML Document Header (required)

<?xml version="1.0" encoding="UTF-8"?>
<ContinuityOfCareRecord xmlns="urn:astm-org:CCR">

<CCRDocumentObjectID>

Hierarchy

/ContinuityOfCareRecord/CCRDocumentObjectID

Syntax

<CCRDocumentObjectID>...</CCRDocumentObjectID>  <!-- any numeric or alphanumeric string -->

Description

"The CCR and all Data Objects contained within the CCR must have ObjectIDs. The CCR Document Object ID is generated by the originating entity/system to uniquely identify each explicit instance of a CCR. The uniqueness of this ObjectID is defined within the generating system and must be unique to and within each CCR and ideally should be unique across the universe of all CCRs."

(TABLE A1.1 CCR Data Fields Spreadsheet, page 9 of the Standard Specification Continuity of Care Record (CCR)).

Child elements

  • None

Example 

<CCRDocumentObjectID>1</CCRDocumentObjectID>

Back to top

<Language>

Hierarchy

/ContinuityOfCareRecord/Language

Syntax 

<Language> 
   <Text>English</Text> <-- The language will be English for some time. --> 
   <Code> 
      <Value>en</Value> 
      <CodingSystem>ISO-639-1</CodingSystem>
   </Code> 
</Language>

Description

Child elements

  • <Text> -- For now, "English."
  • <Code>

Example 

<Language> 
   <Text>English</Text> 
   <Code> 
      <Value>en</Value> 
      <CodingSystem>ISO-639-1</CodingSystem>
   </Code> 
</Language>

Back to top

<Version>

Hierarchy

/ContinuityOfCareRecord/Version

Syntax 

<Version>V1.0</Version>

Description

Currently, we only support <Version>V1.0</Version>.

Child elements

  • None

Example 

<Version>V1.0</Version>

Back to top

<DateTime>

Hierarchy

/ContinuityOfCareRecord/DateTime

Syntax 

<DateTime>
   <ExactDateTime>...</ExactDateTime>
</DateTime>

Description

When a date is sent out from Google, this date represents the date the document was last modified. When importing, the value for ExactDateTime is ignored.

Child elements

Example 

<DateTime>
   <ExactDateTime>2007-01-07T13:00:00-0500</ExactDateTime>
</DateTime>

Back to top

<Patient>

Syntax 

<Patient>
   <ActorID>...</ActorID>
</Patient>

Description

Patient is a placeholder for the identifier of the individual associated with the CCR.

Child elements

Example 

<Patient>
   <ActorID>Patient</ActorID>
</Patient>

Back to top

Footer

The Footer consists of basic demographic information on the patient (name, date of birth, & gender).

The Footer consists of a single supported element, <Actors>.

<Actors>

Hierarchy

/ContinuityOfCareRecord/Actors

Syntax 

<Actors>
   <Actor>...</Actor> unbounded
</Actors>

Description

<Actors> is a "Footer" element only. Currently, this section is ignored on import.

Child elements

Example 

<Actors>
   <Actor>
      <ActorObjectID>Patient</ActorObjectID> 
      <Person> 
         <DateOfBirth> 
            <ExactDateTime>1919-09-21</ExactDateTime>  
         </DateOfBirth> 
         <Gender> 
            <Text>Male</Text> 
            <Code> 
               <Value>248153007</Value> 
               <CodingSystem>SNOMED</CodingSystem> 
            </Code> 
         </Gender> 
      </Person> 
      <Source><Actor><ActorID>Site</ActorID></Actor></Source> 
   </Actor>     
</Actors>

Back to top

Hierarchy

/ContinuityOfCareRecord/Actors/Actor

Syntax 

<Actor>
   <ActorObjectID>...</ActorObjectID>  required
   <Person>...</Person> optional
</Actor>

Description

The <Actor> element appears in two environments:

  1. daughter of <Source>
  2. daughter of <Actors>

<Actors> is a "Footer" element. The syntax and example for <Actor> described here is relevant to the Footer environment. See <Actor> in the "Supported CCR Elements" section, for syntax and example(s) relevant for the <Source> domain.

Child elements

Example 

See the <Actors> example.

Back to top

<ActorObjectID>

Hierarchy

/ContinuityOfCareRecord/Actors/Actor/ActorObjectID

Syntax

<ActorObjectID>...</ActorObjectID>

Description

ActorObjectID is the ID of the actor.

Child elements

  • None

Example 

See the <Actors> example.

Back to top

<Person>

Hierarchy

/ContinuityOfCareRecord/Actors/Actor/Person

Syntax

<Person> 
   <DateOfBirth>...</DateOfBirth> 
   <Gender>...</Gender> 
</Person>

Description

The Person element contains patient information such as "date of birth," and "gender."

Child elements

Example 

See the <Actors> example.

Back to top

<DateOfBirth>

Hierarchy

/ContinuityOfCareRecord/Actors/Actor/Person/DateOfBirth

Syntax

 
<DateOfBirth>...</DateOfBirth>

Description

Format is ISO-8601 (CCYY-MM-DDThh:mm:ssZ (Zulu); CCYY-MM-DDThh:mm:ss-hh:mm (non-Zulu)).

Child elements

  • None

Example 

See the <Actors> example.

Back to top

<Gender>

Hierarchy

/ContinuityOfCareRecord/Actors/Actor/Person/Gender

Syntax

 
<Gender>...</Gender>

Description

The SNOMED code for "Male" is 248153007, and the code for "Female" is 248152002.

Child elements

  • None

Example 

See the <Actors> example.

Back to top

Supported CCR Elements

<Actor>

Hierarchy

/ContinuityOfCareRecord/Body/.../Source/Actor

See Source for the possible elements that can appear in "..."

Syntax 

<Actor>
   <ActorID>...</ActorID>
   <ActorRole>...</ActorRole>
</Actor>

Description

The identifier of the individual associated with the CCR.

The <Actor> element appears in two environments:

  1. daughter of <Source>
  2. daughter of <Actors>

The syntax and example for <Actor> described here is relevant to the Body environment, and appears as a daughter element of <Source>. See <Actor> in the Footer section, for syntax and example(s) relevant for that domain.

Child elements

Examples

This example can occur when embedded under <Medication>.

<Source>
   <Actor>
      <ActorID>Cecil Baker</ActorID>
      <ActorRole><Text>Prescribing clinician</Text></ActorRole> 
      <!--The name of the prescribing clinician goes in Medication/Source/Actor/ActorID--> 
   </Actor>
</Source>

Examples

This example can occur when embedded under <Result>, <Immunization>.

<Source>
   <Actor>
      <ActorID>Cecil Baker</ActorID> 
      <ActorRole><Text>Ordering clinician</Text></ActorRole>
   </Actor>
</Source>

This example can occur when embedded under <Problem>, <Alert>, <Procedure>.

<Source>
   <Actor>
      <ActorID>Cecil Baker</ActorID> 
      <ActorRole><Text>Treating clinician</Text></ActorRole>
   </Actor>
</Source>

Back to top

<ActorID>

Hierarchy

See Source for the possible hierarchies that can appear in "..."

Syntax 

<ActorID>...</ActorID>

Description

The ActorID is a first name followed by a last name (e.g., "Bonnie Jones")

Child elements

  • None

Example 

See the three examples here for different contexts in which the <ActorID> 
can appear.

Back to top

<ActorRole>

Hierarchy

/ContinuityOfCareRecord/Body/.../Source/Actor/ActorRole

Syntax

<ActorRole>
   <Text>...</Text> <!-- type=string -->
</ActorRole>

Description

<ActorRole> specifies the relationship between the clinician and the patient. The supported values are:

  • Ordering clinician
  • Prescribing clinician
  • Treating clinician

Child elements

  • <Text>

Example

See the three examples here for different contexts in which 
the <ActorRole> can appear, and how its value is impacted.

Back to top

<Alert>

Hierarchy

/ContinuityOfCareRecord/Body/Alerts/Alert

Syntax 

<Alert>
   <DateTime> 
      <Type><Text>...</Text></Type>  
      <ExactDateTime>...</ExactDateTime>
   </DateTime> 
   <Type><Text>...</Text></Type>  required value is "Allergy"
   <Description>
      <Text>...</Text>
      <Code>
        <CodingSystem>...</CodingSystem>
        <Value>...</Value>
      </Code>
   </Description> 
   <Status><Text>...</Text></Status> optional
   <Source>
      <Actor><ActorID>...</ActorID></Actor>
      <ActorRole>...</ActorRole>
   </Source> optional
   <Reaction> 
      <Severity><Text>...</Text></Severity>
   </Reaction> optional
</Alert>

Description

<Alert> encodes allergies, and currently none of the other types. This is why <Type> is always "Allergy."

Child elements 

See the <Alert> example.

Back to top

<Alerts>

Hierarchy

/ContinuityOfCareRecord/Body/Alerts

Syntax 

<Alerts>
   <Alert>...</Alert> unbounded
</Alerts>

Description

Child elements

Example

Example involving a medication allergy: 

<Alerts>
   <Alert>
      <DateTime>
         <Type><Text>Start date</Text></Type> <!--There is no "Stop date," which indicates the patient is still allergic to the medication -->
         <ExactDateTime>2007-04-04T07:00:00Z</ExactDateTime>
      </DateTime>
      <Type><Text>Allergy</Text></Type> 
      <Status><Text>Active</Text></Status> <!--or "Inactive" -->
      <Source>
         <Actor><ActorID>Cecil Baker</ActorID></Actor>
         <ActorRole>Treating clinician</ActorRole>
      </Source>
      <Description>
         <Text>Amoxicillin</Text>
         <Code>
            <CodingSystem>NDC</CodingSystem>
            <Value>68387043040</Value>
         </Code>
      </Description> 
      <Reaction>
         <Severity><Text>Severe</Text></Severity>
      </Reaction>
   </Alert>
</Alerts>

Example involving an "egg" allergy that has been outgrown:

<Alerts>
   <Alert>
      <DateTime>
         <Type><Text>Start date</Text></Type>
         <ExactDateTime>2000-04-04T07:00:00Z</ExactDateTime>
      </DateTime>
      <DateTime>
         <Type><Text>Stop date</Text></Type> 
         <ExactDateTime>2007-05-06T08:00:00Z</ExactDateTime>
      </DateTime>
      <Type><Text>Allergy</Text></Type> 
      <Status><Text>Inactive</Text></Status> 
      <Source>
         <Actor><ActorID>Cecil Baker</ActorID></Actor>
         <ActorRole>Treating clinician</ActorRole>
      </Source>
      <Description>
         <Text>Egg</Text>
      </Description> 
      <Reaction>
         <Severity><Text>Severe</Text></Severity>
      </Reaction>
   </Alert>
</Alerts>

Back to top

<Body>

Hierarchy

/ContinuityOfCareRecord/Body/

Syntax 

<Body>
   <FunctionalStatus>...</FunctionalStatus> optional
   <Problems>...</Problems> optional
   <SocialHistory>...</SocialHistory> optional
   <Alerts>...</Alerts> optional
   <Medications>...</Medications> optional
   <Immunizations>...</Immunizations> optional
   <VitalSigns>...</VitalSigns> optional
   <Results>...</Results> optional
   <Procedures>...</Procedures> optional
</Body>

Description

The medical history details are contained in the <Body>.

Child elements

Example 

See Complete example

Back to top

<CCRDataObjectID>

NOTE:Any CCRDataObjectIDs received by Google Health will be dropped.

Back to top

<Code>

Hierarchy


Note:<Code> is an element belonging to the CodedDescriptionType. Elements occurring under the <Body> element that are of this type are: <Description>, <Dose>, and <Route>.

Syntax 

<Code>
   <Value>...</Value>               
   <CodingSystem>...</CodingSystem>
</Code>

Description

A unique industry standard code is needed for each entry so that different systems can agree on how to differentiate between, for example, Diabetes and Measles. There is also the option to provide a text representation of the code, such as "Diabetes." There are many different coding systems in use by the medical community. Our plan is to support at least one of the existing coding systems for each category of medical information (medications, conditions, etc.).

Child elements

Examples

<Code> in the "Header":

<Language> 
   <Text>English</Text> 
   <Code> 
      <Value>en</Value> 
      <CodingSystem>ISO-639-1</CodingSystem>
   </Code> 
</Language>

<Code> under <Medication>:

<ProductName> 
   <Text>Ibuprofen</Text> 
   <Code> 
      <Value>198405</Value>               
      <CodingSystem>RxNorm</CodingSystem> 
   </Code> 
</ProductName>

<Code> under <Problem>:

<Description>
   <Text>Diabetes</Text> 
   <Code> 
      <Value>250.0</Value>               
      <CodingSystem>ICD9</CodingSystem> 
   </Code> 
</Description>

<Code> under <Procedure>:

<Description>
   <Text>Appendectomy</Text> 
   <Code> 
      <Value>144950</Value>               
      <CodingSystem>CPT</CodingSystem> 
   </Code> 
</Description>

<Code> under <Result>/<Description>:

<Result>
<Description>
   <Text>...</Text> 
   <Code> 
      <Value>...</Value>               
      <CodingSystem>...</CodingSystem> 
   </Code> 
</Description>
</Result>

<Code> under <Result>/<Test>/<Description>:

<Test>
   <DateTime>
      <Type>
         <Text7gt;Collection start date</Text7gt;
      </Type>
         <ExactDateTime>2007-02-21</ExactDateTime>
   </DateTime>
   <Description>
      <Text>Spun hematocrit</Text> 
      <Code> 
         <Value>4545-0</Value>               
         <CodingSystem>LOINC</CodingSystem> 
      </Code> 
   </Description>
   <TestResult>
      <Value>40</Value>
      <Units>
         <Unit>%</Unit>
      </Units>
   </TestResult>
</Test>

<Code> in the "Footer":

<Gender> 
   <Text>Male</Text> 
   <Code> 
      <Value>248153007</Value>               
      <CodingSystem>SNOMED</CodingSystem> 
   </Code>  
</Gender>

Back to top

<CodingSystem>

Hierarchy

Under the <Body> element, <CodingSystem> is a daughter of <Code>. Therefore, wherever <Code> can appear in the hierarchy, <CodingSystem> can as well.

Syntax 

<CodingSystem>...</CodingSystem> <--type=string-->

Description

The following coding systems are supported for Diagnoses:

Coding System Description
SNOMEDCT
  • public/free for use within United States
  • ownership recently transferred from College of American Pathologists to the International Health Terminology Standards Development Organization: http://www.ihtsdo.org/. Many countries have committed to paying for country-wide licenses, see site for details.

This will be included when possible.
SNOMEDCT_broader This will be included (only on export) when the best match for the consumer term is a SNOMED code that is broader. For example, 'aspiration pneumonia' would be marked as 233604007 (code for 'pneumonia').
ICD9_Narrower

This will be included when possible.
ICD9_broader This will be included (only on export) when the best match for the consumer term is a ICD9 code that is broader. For example, 'aspiration pneumonia' would be marked as 486 (code for 'Pneumonia organism unspecified')

The following coding systems are supported for Drugs & Allegeries:

Coding System Description
NDC

Our use of this representative NDC code (for example, 00083-0079-90) ignores manufacturer and packaging information. If the form, strength, & route are also known, we will attempt to use an NDC code that can be mapped to an RxNorm code.
NDC_nameonly NDC_nameonly is included if the strength, route, and/or form are unknown. This NDC code is representative only of the medication name, and not of the strength, route, form, manufacturer, or packaging.
RxNorm

This code will only be included if the form, strength, & route are also known. (For example, RxNorm CUI 207792 for the Branded Drug "benazepril 20 mg Oral Tablet [Lipitor]", or RxNorm CUI 308609 for the Clinical Drug "benazepril 20 mg Oral Tablet".
RxNorm_nameonly Only included if the strength, route, and/or form are unknown. We will use the less specific RxNorm code for Brand Name (for branded drug).
FDB

This is the FDB code corresponding to the medication. When CodingSystem="FDB", the FDB code indicates only the name of the medication.
FDB_routed This is the FDB code corresponding to the medication and the route (e.g. oral). Codes with CodingSystem="FDB_routed" are more specific than codes with CodingSystem="FDB".
FDB_dispensable This is the FDB code corresponding to the medication, the route (e.g., oral), and the dosage. Codes with CodingSystem="FDB_dispensable" are more specific than codes with CodingSystem="FDB_routed".

The following coding systems are supported for Lab Tests & Procedures:

Coding System Description
CPT This code set will primarily used to code procedures.
LOINC

Other coding systems supported:

Coding System Description
HL7 only using race codes, freely available: http://www.hl7.org/v3ballot/html/infrastructure/vocabulary/Race.htm

Child elements

  • None

Examples 

See the <Code> examples.

Back to top

<DateTime>

Hierarchy

<DateTime> appears under all daughters of the <Body> element.

Syntax 

<DateTime>
   <Type><Text>...</Text></Type>
   <ExactDateTime>...</ExactDateTime>
</DateTime>

Description

DateTime indicates when and event occurred. For example, when DateTime/Type = "Start date," the value for ExactDateTime indicates when the patient started taking the medication, starting having a condition, etc.

Child elements

  • <Type> -- For possible values, see examples for the <Type> element under <DateTime>.
  • <ExactDateTime> -- We use the ISO-8601 standard representation, (CCYY-MM-DDThh:mm:ssZ (Zulu); CCYY-MM-DDThh:mm:ss-hh:mm (non-Zulu) ).

Example 

See DateTime examples under <Type>.

Back to top

<Description>

Hierarchy

Syntax 

<Description>
   <Text>...</Text>
   <Code>...</Code>
</Description>

Description

<Description> is an element belonging to the CodedDescriptionType.

Child elements

Example 

See <Procedures> example

Back to top

<Direction>

Hierarchy

Syntax 

<Direction>
   <Dose>...</Dose>
   <Route>...</Route>
   <Frequency>...</Frequency>
</Direction>

Child elements

  • <Dose> -- Contains the <Value>, and <Units> elements. Note: Possible values for <Dose> are {".25" | ".5" | "1" | "1.5" | "2" | "3" | ... any positive integer value }.
  • <Route> -- Contains the <Text> element. See the Route table for a list of the possible values a consumer can choose from in the UI.
  • <Frequency> -- In the text field, we will frequency, for example, "1 time," "1 time per day." See the Frequency table for possible values, all with associated SNOMEDCT values

Example 

See the <Directions> example.

Back to top

<Directions>

Hierarchy

Syntax 

<Directions>
   <Direction>...</Direction>  <!-- Only one <Direction> is supported -->
</Directions>

Description

Child elements

Example 

<Directions>
   <Direction>
     <Dose><Value>1</Value><Units><Unit>tablet</Unit></Units></Dose>
     <Route><Text>Oral</Text></Route>
     <Frequency><Value>1 time per day</Value></Frequency>
   </Direction> 
</Directions>

Back to top

<DisplayName>

Hierarchy

Syntax

<DisplayName>name</DisplayName>

Example 

<DisplayName>John Smit</DisplayName>

Back to top

<Dose>

Hierarchy

Syntax 

<Dose>
   <Value>...</Value>
   <Units>
      <Unit>...</Unit>
   </Units>
</Dose>

Description

Child elements

Example 

<Dose>
   <Value>1</Value>
   <Units>
      <Unit>tablet</Unit>
   </Units>
</Dose>

Back to top

<ExactDateTime>

Hierarchy

/ContinuityOfCareRecord/Actors/Actor/Person/DateOfBirth/ExactDateTime (Footer) /ContinuityOfCareRecord/Body/.../DateTime/ExactDateTime

Syntax 

<ExactDateTime>...</ExactDateTime>

Description

The ISO-8601 standard is used to represent either the universal coordinated time (Zulu), or a particular time zone.

Time Time string
Zulu CCYY-MM-DDThh:mm:ssZ
Non-Zulu time (particular time zone) CCYY-MM-DDThh:mm:ss-hh:mm

Child elements

  • None

Examples

Universal Coordinated Time (Zulu)

<ExactDateTime>2007-04-04T07:00:17Z</ExactDateTime>

Pacific Standard Time

<ExactDateTime>2007-04-04T07:00:17-09:00</ExactDateTime>

Back to top

<Form>

Hierarchy

/ContinuityOfCareRecord/Body/Medications/Medication/Product/Form

Syntax

<Form>
   <Text>...</Text>
</Form>

Child elements

  • <Text> -- In the text field, we will provide just the name of the form, for example, "Capsule," "Gum." The possible values a consumer can choose from in our UI are:
    • FDA Code FDA Name Consumer Term
    C25158 CAPSULE Capsule
    C42998 TABLET Tablet
    C42953 LIQUID Liquid
    C28944 CREAM Cream
    C42934 GEL Gel
    C29167 LOTION Lotion
    C42966 OINTMENT Ointment
    C42953 LIQUID Liquid
    C42944 INHALANT Inhalant
    C42946 INJECTION Injection
    C42941 GUM Gum
    C42955 LOZENGE Lozenge
    C29269 MOUTHWASH Mouthwash
    C42888 AEROSOL, FOAM Foam
    C42968 PATCH Patch
    C42989 SPRAY Spray
    C42981 SHAMPOO Shampoo
    C42983 SOAP Soap
    C47898 SWAB Swab
    C47897 TAPE Tape
    C42915 ENEMA Enema
    C42972 POWDER Powder
    C42942 IMPLANT Implant
    C47915 INTRAUTERINE DEVICE Intrauterine device (IUD)
    C60988 RING Ring
    C47912 SPONGE Sponge
    C42993 SPONGE Suppository

Example 

<Form><Text>Tablet</Text></Form>

Back to top

<Frequency>

Hierarchy

/ContinuityOfCareRecord/Body/Medications/Medication/Directions/Direction/Frequency

Syntax 

<Frequency><Value>...</Value></Frequency>

Description

This element denotes the frequency with which a medication should be taken.

Child elements

  • <Value> -- Google provides just the name of the frequency, for example, "1 time," "1 time per day." Possible values, all with associated SNOMEDCT values:
    • Consumer Description SNOMEDCT Synonyms we will try to understand
    1 time per day 229797004 qd; qday; daily
    1 time per day in the morning 307472001 qam
    1 time per day in the evening 396147000 qpm
    1 time per day at bedtime 396142006 qhs
    2 times per day 229799001 bid
    3 times per day 229798009 tid
    3 times per day, before meals 396145008
    3 times per day, with meals 396146009
    4 times per day 307439001 qid
    every 2 hours 225750008 q2
    every 4 hours 225756002 q4
    every 6 hours 307468000 q6
    every 8 hours 307469008 q8
    every 12 hours 307470009 q12
    every other day 225760004 qod
    1 time per week 225769003
    every two weeks 20050000
    every 28 days 307476003
    every month 307475004
    as needed 420449005 prn
    1 time 422114001 once

Example 

See the Directions example.

Back to top

<Fulfillment>

Hierarchy

/ContinuityOfCareRecord/Body/Medications/Medication/FulfillmentHistory/Fulfillment

Syntax 

<Fulfillment>
   <Quantity>...</Quantity>
   <DateTime>...</DateTime>
</Fulfillment>

Description

<Fulfillment> describes a single dispensing of a particular medication. If a pharmacy fills a prescription multiple times, the pharmacy should provide a separate instance of <Fulfillment> for each refill.

Child elements

Example

See FulfillmentHistory example

Back to top

<FulfillmentHistory>

Hierarchy

/ContinuityOfCareRecord/Body/Medications/Medication/FulfillmentHistory

Syntax 

<FulfillmentHistory>
   <Fulfillment>...</Fulfillment>
</FulfillmentHistory>

Description

"Defines the fulfillment history of the <Product>." (Table A1.1, page 25 of the Standard Specification Continuity of Care Record (CCR).

Child elements

Example

<FulfillmentHistory>
   <Fulfillment>
      <Quantity>
         <Value>30</Value>
         <Units>
            <Unit>
               <Unit>Tablet</Unit>
            </Unit>
         </Units>
      </Quantity>
      <DateTime>
         <Type><Text>Dispense date</Text></Type>
         <ExactDateTime>2007-05-02T07:00:00Z</ExactDateTime>
      </DateTime>
   </Fulfillment> 
</FulfillmentHistory>

Back to top

<Function>

Hierarchy

/ContinuityOfCareRecord/Body/FunctionalStatus/Function

Syntax 

<Function>      
   <DateTime>...</DateTime> optional
   <Description>...<Description> optional
   <Status>...</Status> required
</Function>

Description

Google used the <Function> element to indicate whether the user has specified she is pregnant, or breastfeeding.

Child elements

Example 

See the FunctionalStatus example.

Back to top

<FunctionalStatus> optional

Hierarchy

/ContinuityOfCareRecord/Body/FunctionalStatus

Syntax 

<FunctionalStatus>
   <Function></Function>  unbounded
</FunctionalStatus>

Description

When imported by Google Health, these values are not reconciled. However, if the user has entered these values via the UI, they will be available on an outgoing basis.

Child elements

Example 

<FunctionalStatus>
   <Function>
      <Type>Pregnancy status</Type>
      <Description>  optional
         <Text>Pregnant</Text>
         <Code>
            <Value>77386006</Value>
            <CodingSystem>SNOMEDCT</CodingSystem>
         </Code>
      </Description>
      <Status><Text>Active</Text></Status>  required 
   </Function> 
   <Function>
       <Type>Breastfeeding status</Type>
      <Description>
         <Text>Breastfeeding</Text>
         <Code>
            <Value>169750002</Value>
            <CodingSystem>SNOMEDCT</CodingSystem> 
         </Code>
      </Description>
      <Status><Text>Active</Text></Status>
   </Function>
</FunctionalStatus>

Back to top

<ID>

Hierarchy

Syntax

<ID>value</ID>

Example

See the <Payers> example.

<IDs>

Hierarchy

Syntax

<IDs>
  <Type>...</Type>
  <ID>...</ID>
</IDs>

Description

Child elements

Example

See the <Payers> example.

<Immunization>

Hierarchy

/ContinuityOfCareRecord/Body/Immunizations/Immunization

Syntax

<Immunization>
   <DateTime>... </DateTime>
   <Source>...</Source>
   <Product>...</Product>
</Immunization>

Description

Each <Immunization> element represents on immunization administration.

Child elements

Example 

See the <Immunizations example> example.

Back to top

<Immunizations>

Hierarchy

/ContinuityOfCareRecord/Body/Immunizations

Syntax 

<Immunizations>
   <Immunization>... </Immunization> unbounded
</Immunizations>

Child elements

Example 

<Immunizations>
   <Immunization>
      <DateTime>
         <Type><Text>Start date</Text></Type>
         <ExactDateTime>2007-04-04T07:00:00Z</ExactDateTime>
      </DateTime>
      <Source>
         <Actor>
            <ActorID>Alex Smith</ActorID>
            <ActorRole><Text>Ordering clinician</Text></ActorRole>
         </Actor>
      </Source>
      <Product>
         <ProductName>
            <Text>Hepatitis A vaccine</Text>
            <Code>
               <Value>90633</Value>
               <CodingSystem>CPT</CodingSystem>
            </Code>
         </ProductName>
      </Product>
   </Immunization>
</Immunizations>

Back to top

<Medication>

Hierarchy

/ContinuityOfCareRecord/Body/Medications/Medication

Syntax 

<Medication>
    <Status>...</Status> optional
    <DateTime>...</DateTime> optional
    <Source>...</Source>  optional
    <Product>...</Product> optional
    <Directions>...</Directions> optional
    <FulfillmentHistory>...</FulfillmentHistory> optional
</Medication>

Description

Each <Medication> element represents a medication the user is takeing, or has taken.

Child elements

See the <Medications> example.

Back to top

<Medications>

Hierarchy

/ContinuityOfCareRecord/Body/Medications

Syntax 

<Medications>
   <Medication>...</Medication> unbounded
</Medications>

Description

Child elements

Example

Example 

<Medications> 
   <Medication> 
    <Status><Text>Active</Text></Status>
    <DateTime>
      <Type><Text>Prescription Date</Text></Type>
      <ExactDateTime>2007-04-01T05:00:00Z</ExactDateTime>
    </DateTime>
    <Source>
       <Actor>
          <ActorID>Cecil Baker</ActorID>
       </Actor>
       <ActorRole>Prescribing clinician</ActorRole>
    </Source> 
      <Product> 
         <ProductName> 
            <Text>Ibuprofen</Text> 
            <Code> 
               <Value>198405</Value> 
               <CodingSystem>RxNorm</CodingSystem> 
            </Code> 
         </ProductName> 
         <Strength>
            <Value>100</Value>
            <Units>
               <Unit>mg</Unit>
            </Units>
         </Strength> 
         <Form>
            <Text>Tablet</Text>
         </Form> 
      </Product> 
      <Directions>
         <Direction>
            <Dose>
               <Value>1</Value>
               <Units>
                  <Unit>tablet</Unit>
               </Units>
            </Dose>
            <Route><Text>Oral</Text></Route>
            <Frequency><Value>1 time per day</Value></Frequency>  <!-- Note: if Frequency/Value is null,
         </Direction>                                                  the value in Medication/Frequency/Description/Text
      </Directions>                                                    will be accepted. -->
      <FulfillmentHistory>
         <Fulfillment>
            <Quantity>30</Quantity>
            <DateTime>
               <Type><Text>Dispense date</Text></Type>
               <ExactDateTime>2007-06-01T06:00:00Z</ExactDateTime>
            </DateTime>
         </Fulfillment>
      </FulfillmentHistory> 
   </Medication>
</Medications>

Back to top

<Name>

Hierarchy

Syntax

<Name>value</Name>

Child elements

Example

See Organization example

<NormalResult>

Hierarchy

Syntax

  <NormalResult>
    <Value>...</Value>  
    <Units>...</Units>   
  </NormalResult>

Child elements

Example 

See example of <Result> under <Results>. 
See example of <Result> under <VitalSigns>.

Back to top

<Organization>

Hierarchy

Syntax

  <Organization>
    <Name>...</Name>
  </Organization>

Child elements

Example 

  <Organization>
    <Name>Blue Shield</Name>
  </Organization>

Back to top

<Payer>

Hierarchy

/ContinuityOfCareRecord/Body/Payers/Payer

Syntax

<Payer>
   <DateTime>...</DateTime>
   <Description>...</Description>
   <IDs>...</IDs>
   <Type>...</Type>
   <Status>...</Status>
   <Subscriber>...</Subscriber>
</Payer>

Child elements

Notes

Possible values for Payer/Type include: "Primary Health Insurance", "Supplemental Health Insurance", "Prescription Drug Benefit", "Dental Insurance", "Vision Insurance", "Other"

Example

See example of <Payer> under <Payers>.

Back to top

<Payers>

Hierarchy

/ContinuityOfCareRecord/Body/Payers

Syntax

<Payers>
   <Payer>...</Payer>
</Payers>

Child elements

Example 

<Payers>
  <Payer>
    <DateTime>
      <Type><Text>Start date</Text></Type>
      <ExactDateTime>2007-04-04</ExactDateTime>
    </DateTime>
    <DateTime>
      <Type><Text>Stop date</Text></Type>
      <ExactDateTime>2007-11-02</ExactDateTime>
    </DateTime>
    <IDs>
      <Type><Text>Plan code</Text></Type>
      <ID>255</ID>
    </IDs>
    <IDs>
      <Type><Text>Group number</Text></Type>
      <ID>A155</ID>
    </IDs>
    <IDs>
      <Type><Text>Subscriber number</Text></Type>
      <ID>B78-35-66</ID>
    </IDs>
    <Type>
      <Text>Primary Health Insurance</Text> (<!-- required, see accepted values -->)
    </Type>
    <Description>
      <Text>HMO</Text>
    </Description>
    <Status>
      <Text>Active</Text>
    </Status>
    <PaymentProvider>
      <ActorID>#provider actor id#</ActorID>
    </PaymentProvider>
    <Subscriber>
      <ActorID>#subscriber actor id#</ActorID>
    </Subscriber>
  </Payer>
<Payers>

Back to top

<PaymentProvider>

Hierarchy

Syntax 

<PaymentProvider>
    <ActorID>...</ActorID>
</PaymentProvider>

Description

Child elements

See the example in the Payers section.

Back to top

<Problem>

Hierarchy

/ContinuityOfCareRecord/Body/FunctionalStatus/Problems/Problem

Syntax

<Problem>
  <DateTime>...</DateTime>  optional
  <Description>...</Description> optional  
  <Status>...</Status> optional
  <Source></Source>  optional
</Problem>

Description

The element for recording each condition and symptom is <Problem>.

Child elements

Example

See the Problems example.

Back to top

<Problems>

Hierarchy

/ContinuityOfCareRecord/Body/Problems

Syntax 

<Problems>
   <Problem>...</Problem>
    unbounded
</Problems>

Description

Child elements

Example 

<Problems>
  <Problem>
    <DateTime>
      <Type><Text>Start date</Text></Type>
      <ExactDateTime>2007-04-04T07:00:00Z</ExactDateTime>
    </DateTime>
    <Description>
      <Text>Aortic valve disorders</Text>
      <Code>
        <Value>410.10</Value>
        <CodingVersion>ICD9</CodingVersion>
        <Version>2004</Version>
      </Code>
    </Description>  
    <Status><Text>Active</Text></Status>
    <Source>
      <Actor>
        <ActorID>Cecil Baker</ActorID>
        <ActorRole>
          <Text>Treating clinician</Text>
        </ActorRole>
      </Actor>
    </Source>
  </Problem>
</Problems>

Back to top

<Procedure>

Hierarchy

Syntax 

<Procedure>
    <DateTime>...</DateTime>
    <Description>...</Description>
    <Source>...</Source>
</Procedure>

Description

Child elements

See the example in the Procedures section.

Back to top

<Procedures>

Hierarchy

/ContinuityOfCareRecord/Body/Procedures

Syntax 

<Procedures> 
   <Procedure> ... <Procedure> unbounded
</Procedures>

Child elements

Example 

<Procedures>
  <Procedure>
    <DateTime>
       <Type><Text>Start date</Text></Type>
       <ExactDateTime>2007-04-04T07:00:00Z</ExactDateTime>
    </DateTime>
    <Description>
      <Text>Appendectomy</Text>
      <Code>
        <Value>144950</Value>
        <CodingSystem>CPT</CodingSystem>
      </Code>
    </Description>
    <Source>
       <Actor>
          <ActorID>Carol Smith</ActorID>
          <ActorRole>Treating clinician</ActorRole>
       </Actor>
    </Source>
  </Procedure>
</Procedures>

Back to top

<Product>

Hierarchy

Syntax 

<Product> 
   <ProductName> required
      <Text>...</Text> 
      <Code> 
         <Value>...</Value> 
         <CodingSystem>...</CodingSystem> 
      </Code> 
   </ProductName> 
   <Strength>  <!-- under <Medication> only -- >
      <Value>...</Value>
      <Units>
         <Unit>...</Unit>
      </Units>
   </Strength> 
   <Form><Text>...</Text></Form> <!-- under <Medication> only -- >
</Product>

Description

Child elements

  • <ProductName>
  • <Strength> -- This element occurs under <Medication> only.
  • <Form> -- This element occurs under <Medication> only.

Example under <Medication>

<Product> 
   <ProductName> 
      <Text>Ibuprofen</Text> 
      <Code> 
         <Value>198405</Value> 
         <CodingSystem>RxNorm</CodingSystem> 
      </Code> 
   </ProductName> 
   <Strength>
      <Value>100</Value>
      <Units>
       <Unit>mg</Unit>
    </Units>
   </Strength> 
   <Form>
      <Text>Tablet</Text>
   </Form> 
</Product>

Back to top

<ProductName>

Hierarchy

Syntax 

<ProductName> 
   <Text>...</Text> 
   <Code> 
      <Value>...</Value> 
      <CodingSystem>...</CodingSystem> 
   </Code> 
</ProductName>

Description

Child elements

  • <Text> -- In the text field, we will provide just the name of the medication, for example, "Benazepril," "Lipitor."
  • <Code> -- Contains the <Value>, and <CodingSystem> elements. There are two coding systems, "NDC," and RxNorm." (See Table under <CodingSystem>. When uploading to Google, we will use, in order of preference: RxNorm, NDC, and FDB.

Example 

<ProductName> 
   <Text>Ibuprofen</Text> 
   <Code> 
      <Value>198405</Value> 
      <CodingSystem>RxNorm</CodingSystem> 
   </Code> 
</ProductName>

Back to top

<Quantity>

Hierarchy

/ContinuityOfCareRecord/Body/Medications/Medication/FulfillmentHistory/Fulfillment/Quantity

Syntax 

<Quantity>
   <Value>...</Value>
   <Units>...</Units>
</Quantity>

Description

Includes the quantity of the medication dispensed.

Child elements

Example

<Quantity>
   <Value>30</Value>
   <Units
      <Unit>Tablet</Unit>
   </Units>
</Quantity>

Back to top

<Reaction>

Hierarchy

/ContinuityOfCareRecord/Body/Alerts/Alert/Reaction

Syntax 

   <Reaction>
      <Severity>...</Severity>
   </Reaction>

Description

Google Health uses <Reaction> to indicate the severity of the reaction.

Child elements

Example 

   <Reaction>
      <Severity><Text>Severe</Text></Severity>
   </Reaction>

Back to top

<Result>

Hierarchy

Syntax 

   <Result>
      <Description> <!-- At this level, <Description> is optional, but in the case of multiple tests, as in a panel, it is useful to include a description here. -->
         <Text>...</Text>
         <Code> 
            <Value>...</Value> 
            <CodingSystem>.../CodingSystem> 
         </Code>
       </Description>
       <Source> optional
          <Actor>
             <ActorID>...</ActorID>
             <ActorRole>...</ActorRole>
          </Actor>
       </Source>   <!--<Source> is not supported under <VitalSigns> -->
       <Test>
          <DateTime> optional 
             <Type><Text>...</Text></Type>
             <ExactDateTime>...</ExactDateTime>  
          </DateTime> 
          <Description>...</Description> required
          <TestResult>
             <Value>..</Value>
             <Units>...</Units>
          </TestResult>
          <NormalResult>
             <Value>...</Value>
             <Units>...</Units>
          </NormalResult>
       </Test>
   </Result>

Description

Ideally, there would be at least one test element. However, in the case of a long lab report (for example, a biopsy report), we will request that the sender not send us a result, but only the test ID and date.

Child elements 

See example of <Result> under <Results>. 
See example of <Result> under <VitalSigns>.

Back to top

<Results>

Hierarchy

/ContinuityOfCareRecord/Body/Results

Syntax 

<Results>
   <Result>... </Result> unbounded
</Results>

Description

Child elements

Example 

<Results>
   <Result>
      <Description> 
 <!-- Result/Description is only used for the
name of the panel (i.e., in the case of multiple tests). -->
         <Text>Hemogram panel</Text>
         <Code> 
            <Value>24358-4</Value> 
            <CodingSystem>LOINC</CodingSystem> 
         </Code>
       </Description>
       <DateTime>
      <Type><Text>Collection start date</Text></Type>
      <ExactDateTime>2007-07-01T04:00:00Z</ExactDateTime>
      </DateTime>
       <Source>
          <Actor>
            <ActorID>Cecil Baker</ActorID>
            <ActorRole>Ordering clinician</ActorRole>
          </Actor>
       </Source>
       <Test> 
          <Description> 
            <Text>Leukocytes</Text>
            <Code> 
                <Value>26464-8</Value> 
                <CodingSystem>LOINC</CodingSystem> 
            </Code>
          </Description>
          <TestResult>
            <Value>6400</Value>
            <Units>cells/microlite</Units>
          </TestResult>
          <NormalResult>Leukocytes: 4,000-10,000 cells/microliter</NormalResult> 
       </Test>
       <Test> 
          <Description> <
             <Text>Hemoglobin</Text>
             <Code> 
                <Value>718-7</Value> 
                <CodingSystem>LOINC</CodingSystem> 
             </Code>
          </Description>
          <TestResult>
             <Value>15.6</Value>
             <Units>gm/dL</Units>
          </TestResult>
          <NormalResult>...</NormalResult>
       </Test>
   </Result>
</Results>

Back to top

<Route>

Hierarchy

Syntax 

<Route><Text>...</Text></Route>

Description

In the text field, Google provides just the name of the route, for example, "By mouth." The table below lists possible values consumers can choose from when they select a medication.

Child elements

  • <Text>
    • FDA Code FDA Name Consumer Name
    C38288 ORAL By mouth
    C38287 OPHTHALMIC To eyes
    C38304 TOPICAL To skin
    C38192 AURICULAR (OTIC) To ears
    C38284 NASAL To nose
    C28161 INTRAMUSCULAR Into the muscle
    C38216 RESPIRATORY (INHALATION) Inhaled
    C38305 TRANSDERMAL To skin
    C38276 INTRAVENOUS Intravenous
    C38223 INTRA-ARTICULAR Into a joint
    C38313 VAGINAL To vagina
    C38299 SUBCUTANEOUS Into the skin
    C38295 RECTAL Rectal
    C38238 INTRADERMAL Into the skin
    (none) Implant under the skin
    C38300 /td> SUBLINGUAL Under the tongue
    C38200 HEMODIALYSIS Hemodialysis
    C38210 EPIDURAL Epidural
    C38222 INTRA-ARTERIAL Into an artery
    C38255 INTRAOCULAR Into the eye
    C38278 INTRAVESICAL Into the bladder
    C38272 INTRAUTERINE Into the uterus
    C38271 URETHRAL To urethra
    C38208 ENDOTRACHEAL Into the trachea
    C38193 BUCCAL To inner cheek
    C38197 DENTAL Dental
    C38235 INTRACORPORUS CAVERNOSUM Into the penis
    C38258 INTRAPERITONEAL Into the peritoneum
    C38281 IRRIGATION Irrigation
    C38267 INTRATHECAL Intrathecal
    C38259 INTRAPLEURAL Into the pleura

Example 

<Route><Text>Oral</Text></Route>

Back to top

<Severity>

Hierarchy

/ContinuityOfCareRecord/Body/Alerts/Alert/Reaction/Severity

Syntax 

<Severity><Text>...</Text></Severity>

Description

  • In the text field, Google will indicate the level of severity. The only terms Google will display, or accept as input, are "Mild" or "Severe."
  • For coded entries, Google supports SNOMEDCT terms that descend from the severities (272141005) concept. Possible values are { 255604002 : "mild" | 371923003 : "mild to moderate" | 6736007 : | "moderate" | 371924009 : "moderate to severe" | 24484000 : "severe" | 399166001 : "fatal"}. While the user is only allowed to input "Mild" or "Severe," Google accepts any of the values when uploaded to Google. These values are mapped to the following consumer terms, { Mild = mild, mild to moderate; Severe = moderate, moderate to severe, severe, fatal }.
  • When uploading to Google, we will use, in order of preference, SNOMEDCT, text.

Child elements

  • <Text> -- In the text field, Google will indicate the level of severity. The only terms Google will display, or accept as input, are "Mild" or "Severe."

Example 

<Severity><Text>Severe</Text></Severity>

Back to top

<SocialHistory>

Hierarchy

/ContinuityOfCareRecord/Body/SocialHistory

Syntax

<SocialHistory>
   <SocialHistoryElement>...</SocialHistoryElement> unbounded
</SocialHistory>

Description

When imported by Google Health, these values are not reconciled. They will available outgoing if the user has entered these values via the UI.

Child elements

Example 

<SocialHistory>
   <SocialHistoryElement>
      <Type><Text>Race</Text></Type>
      <Description>
         <Text>Asian</Text>
         <Code>
            <Value>515743</Value>
            <CodingSystem>HL7</CodingSystem>
         </Code>
      </Description>
   </SocialHistoryElement></SocialHistory>

Back to top

<SocialHistoryElement>

/ContinuityOfCareRecord/Body/SocialHistory/SocialHistoryElement

Syntax 

<SocialHistory>
   <SocialHistoryElement>
      <Type> optional
         <Text>...</Text>
      </Type>
      <Description> optional
         <Text>...</Text>
         <Code>
            <Value>...</Value>
            <CodingSystem>...</CodingSystem>
         </Code>
      </Description>
   </SocialHistoryElement> 
</SocialHistory>

Description

The <SocialHistoryElement> is only used to indicate race.

Child elements

Example 

See <SocialHistoryElement> example

Back to top

<Source>

Hierarchy

<Source> appears under virtually all daughters of the <Body> element.
That said, the Google implementation of the CCR does not support <Source> under <FunctionalStatus> <VitalSigns> or under <SocialHistory>

Syntax 

<Source>
   <Actor>
      <ActorID>...</ActorID>
      <ActorRole>...</ActorRole>
   </Actor>
</Source>

Description

Child elements

Example

Under <Medication> 

<Source>
   <Actor>
      <ActorID>Cecil Baker</ActorID>
      <ActorRole><Text>Prescribing clinician</Text></ActorRole>  
   </Actor>
</Source>

Under <Problem>, <Alert>, <Procedure>

<Source>
   <Actor>
      <ActorID>Cecil Baker</ActorID>
      <ActorRole><Text>Treating clinician</Text></ActorRole>  
   </Actor>
</Source>

Under <Result>, <Immunization>

<Source>
   <Actor>
      <ActorID>Cecil Baker</ActorID>
      <ActorRole><Text>Ordering clinician</Text></ActorRole>  
   </Actor>
</Source>

Note that "Cecil Baker" in the above examples is a dangling reference since Google Health will not further describe the actor in the footer.

Back to top

<Status>

Hierarchy

Syntax 

<Status><Text>...</Text></Status>

Description

Child elements

  • <Text> -- Example values: "Active", "ACTIVE", "RESOLVED", "Inactive"

Example 

<Status><Text>Active</Text></Status>

Back to top

<Strength>

Hierarchy

Syntax

<Strength>
   <Value>.../Value>
   <Units>...</Units>
</Strength>

Description

Child elements

  • <Value>
  • <Units> -- Contains the <Unit> element. Note that in the <Unit> element, we will provide just the name of the unit, for example, "mg."

When uploading to Google, we will first check if the medication product used NDC or RxNorm. In that case, we will attempt to extract the strength Unit and Value from that code.

Example 

   <Strength>
      <Value>100</Value>
    <Units><
       Unit>mg</Unit>
    </Units>
   </Strength>

Back to top

<Subscriber>

Hierarchy

Syntax

<Subscriber>
   <ActorID>.../ActorID>
</Strength>

Description

Child elements

Example

See Payers for a full example.

Back to top

<Telephone>

Hierarchy

/ContinuityOfCareRecord/Actors/Actor/Telephone

Syntax 

<Telephone>
   <Value>...</Value>
</Telephone>

Child elements

Example 

<Telephone>
   <Value>1-800-700-6000</Value>
</Telephone>

<Test>

Hierarchy

Syntax 

<Test> 
   <DateTime>...</DateTime>
   <Description>...</Description>
   <Source>...</Source>
   <NormalResult>...<NormalResult>
   <TestResult>...</TestResult>
</Test>

Description

Child elements

Example 

<Test>
   <DateTime>
      <Type>
         <Text>Collection start date</Text>
      </Type>
         <ExactDateTime>2007-02-21</ExactDateTime>
   </DateTime>
   <Description> 
      <Text>Spun hematocrit</Text>
      <Code>
         <Value>4545-0</Value>
         <CodingSystem>LOINC</CodingSystem>
      </Code>
   </Description>
   <TestResult>
      <Value>40</Value>
      <Units>
         <Unit>%</Unit>
      </Units>
   </TestResult>
   <NormalResult>
      <Value>40</Value>
         <Units>
            <Unit>%</Unit>
         </Units>
    </NormalResult>
</Test>

Back to top

<TestResult>

Hierarchy

/ContinuityOfCareRecord/Body/FunctionalStatus/Function/Test/TestResult

Syntax 

<TestResult>
   <Value>...</Value>
   <Units>...</Units>
</TestResult>

Description

<TestResult> indicates results for a single instance of a certain test.

Child elements

Example 

<TestResult>
   <Value>9.2</Value>
   <Units>mg/dL</Units>
</TestResult>

Back to top

<Type>

Hierarchy

Syntax 

<Type>
   <Text>...</Text>
</Type>

Description

Child elements

  • <Text>

Type values:

<Type> value Element/
Collection start date
Dispense date
Start date
Stop date
Prescription date
Primary Health Insurance
Supplemental Health Insurance
Prescription Drug Benefit
Dental Insurance
Vision Insurance
Other
Plan code
Group number
Subscriber number

Some examples

Under ResultTest/DateTime, 

<DateTime>
   <Type><Text>Collection start date</Text></Type>
   <ExactDateTime>2007-05-02T07:00:00Z</ExactDateTime>
</DateTime>

Under Fulfillment/DateTime

<DateTime>
   <Type><Text>Dispense date</Text></Type>
   <ExactDateTime>2007-05-02T07:00:00Z</ExactDateTime>
</DateTime>

Under Procedure/DateTime, Alert/DateTime, and Problem/DateTime, and Medication/DateTime 

<DateTime>
   <Type><Text>Stop date</Text></Type>
   <ExactDateTime>2007-05-02T07:00:00Z</ExactDateTime>
</DateTime>

Under Immunization/DateTime, Procedure/DateTime, Alert/DateTime, and Problem/DateTime, and Medication/DateTime

<DateTime>
   <Type><Text>Start date</Text></Type>
   <ExactDateTime>2007-05-02T07:00:00Z</ExactDateTime>
</DateTime>

Under Medication/DateTime

<DateTime>
   <Type><Text>Prescription date</Text></Type>
   <ExactDateTime>2007-05-02T07:00:00Z</ExactDateTime>
</DateTime>

Back to top

<Unit>

Hierarchy

Syntax 

<Unit>...</Unit>

Description

Child elements

  • None

Example 

<Unit>mg</Unit>

Back to top

<Units>

Hierarchy

Syntax 

<Units>
   <Unit>...</Unit>
</Units>

Description

Child elements

Example

<Strength>
     <Value>100</Value>
     <Units>
          <Unit>mg</Unit>
     </Units>
</Strength>

Back to top

<Value>

Hierarchy

Syntax

<Value>...</Value>

Description

<Value> can be either a string or an integer, depending on the context.

Child elements

  • None

Examples 

<ProductName> 
   <Text>Ibuprofen</Text> 
   <Code> 
      <Value>198405</Value> 
      <CodingSystem>RxNormal</CodingSystem> 
   </Code> 
</ProductName> 

<Strength>
   <Value>100</Value>
   <Units>
      <Unit>mg</Unit>
   </Units>
</Strength>

<Directions>
   <Direction>
      <Dose>
         <Value>1</Value>
          <Units>
             <Unit>tablet</Unit>
          </Units></Dose>
      <Route><Text>Oral</Text></Route>
      <Frequency><Value>1 time per day</Value></Frequency>
   </Direction> 
</Directions>

Back to top

<VitalSigns>

Hierarchy

/ContinuityOfCareRecord/Body/VitalSigns

Syntax 

<VitalSigns>
   <Result>...</Result> unbounded
</VitalSigns>

Description

When imported by Google Health, these values are not reconciled. They will available outgoing if the user has entered these values via the UI.

Child elements

Example 

<VitalSigns>
   <Result>      
      <Test>
         <Description>
            <Text>Height</Text>
            <Code>
               <Value>50373000</Value>
               <CodingSystem>SNOMED</CodingSystem>
            </Code>
         </Description>
         <TestResult>
            <Value>72</Value>
            <Units><Unit>in</Unit></Units>
         </TestResult>
      </Test>
   </Result>
   <Result>
      <Test>
          <Description>
            <Text>Weight</Text>
            <Code>
               <Value>363808001</Value>
               <CodingSystem>SNOMED</CodingSystem>
            </Code>
         </Description>
         <TestResult>
            <Value>150</Value>
            <Units><Unit>lbs</Unit></Units>
         </TestResult>
       </Test>
   </Result>
</VitalSigns>

Back to top

Mapping CCR Elements → Google Health UI

Note: All fields are optional except for the Google Health UI 'Name' field. Set the 'Name' field by using the .../.../Description/Text element or by using a valid <Code> value. The later is recommend.

Allergies

See an example screenshot.

This example was created from the complete ccr profile example.

Google Health UIData TypeCCR MappingExample
Namestring/Body/Alerts/Alert/Description/Text

or use a valid <Code> value instead

Penicillins
Severitystring/Body/Alerts/Alert/Reaction/Severity/TextMild
Start datedate/Body/Alerts/Alert/DateTime/ExactDateTime

Note: Alerts/Alert/DateTime/Type/Text
should be set to Start date

2007-02-21T07:00:00Z
End datedate/Body/Alerts/Alert/DateTime/ExactDateTime

Note: Alerts/Alert/DateTime/Type/Text
should be set to Stop date

2008-02-21T07:00:00Z
Treated bystring/Body/Alerts/Alert/Source/Actor/ActorID

Note: Alerts/Alert/Source/Actor/ActorRole/Text
should be set to Treating clinician

Bob Smith

Conditions

See an example screenshot.

This example was created from the complete ccr profile example.

Google Health UIData TypeCCR MappingExample
Namestring/Body/Problems/Problem/Description/Text

or use a valid <Code> value instead

Migraine Headache
Start datedate/Body/Problems/Problem/DateTime/ExactDateTime

Note: Problems/Problem/DateTime/Type/Text
should be set to Start date

2007-04-04T07:00:00Z
End datedate/Body/Problems/Problem/DateTime/ExactDateTime

Note: Problems/Problem/DateTime/Type/Text
should be set to Stop date

2008-07-20T07:00:00Z
Treated Bystring/Body/Problems/Problem/Source/Actor/ActorID

Note: Problems/Problem/Source/Actor/ActorRole/Text
should be set to Treating clinician

Harris Smith

Immunizations

See an example screenshot.

This example was created from the complete ccr profile example.

Google Health UIData TypeCCR MappingExample
Namestring/Body/Immunizations/Immunization/Product/ProductName/Text

or use a valid <Code> value instead

Diphtheria antitoxin
Datedate/Body/Immunizations/Immunization/DateTime/ExactDateTime

Note: Immunizations/Immunization/DateTime/Type/Text
should be set to Start date

1998-06-13T05:00:00Z
Ordered Bystring/Body/Immunizations/Immunization/Source/Actor/ActorID

Note: Immunizations/Immunization/Source/Actor/ActorRole/Text
should be set to Ordering clinician

Jane Smith

Medications

See an example screenshot.

This example was created from the complete ccr profile example.

Google Health UIData TypeCCR MappingExample
Namestring/Body/Medications/Medication/Product/ProductName/Text

or use a valid <Code> value instead

Sotalol oral
Fromdate/Body/Medications/Medication/DateTime/ExactDateTime

Note: Medications/Medication/DateTime/Type/Text
should be set to Start date

2008-06-22T07:00:00Z
todate/Body/Medications/Medication/DateTime/ExactDateTime

Note: Medications/Medication/DateTime/Type/Text
should be set to Stop date

2008-07-10T07:00:00Z
Pill strengthmeasure
unit
type		/Body/Medications/Medication/Strength/Value
and
/Body/Medications/Medication/Strength/Units/Unit
and
/Body/Medications/Medication/Product/Form/Text		160 MG Tablet
Dosageinteger/Body/Medications/Medication/Directions/Direction/Dose2
Frequencystring/Body/Medications/Medication/Directions/Direction/Frequency/Value1 time per day
Routeenum/Body/Medications/Medication/Directions/Direction/Route/TextOral
Refills left integer/Body/Medications/Medication/Refills/Refill/Number2
Written ondate/Body/Medications/Medication/DateTime/ExactDateTime

Note: Medications/Medication/DateTime/Type/Text
should be set to Prescription date

2008-06-21T07:00:00Z
Written bystring/Body/Medications/Medication/Source/Actor/ActorID

Note: Medications/Medication/Source/Actor/ActorRole/Text
should be set to Prescribing clinician

Emily Smith
Filled ondate/Body/Medications/Medication/FulfillmentHistory/Fulfillment/DateTime/ExactDateTime

Note: Medications/Medication/FulfillmentHistory/Fulfillment/DateTime/Type/Text
should be set to Dispense date

2008-06-22T07:00:00Z
Quantitystring/Body/Medications/Medication/FulfillmentHistory/Fulfillment/Quantity/Value30
Prescription IDstring/Body/Medications/Medication/FulfillmentHistory/Fulfillment/IDs/ID

Note: Medications/Medication/FulfillmentHistory/Fulfillment/IDs/ID/Type/Text
should be set to Prescription ID

#92033859

Procedures

See an example screenshot.

This example was created from the complete ccr profile example.

Google Health UIData TypeCCR MappingExample
Namestring/Body/Procedures/Procedure/Description/Text

or use a valid <Code> value instead

Surgical removal of a fingernail or toenail
Datedate/Body/Procedures/Procedure/DateTime/ExactDateTime

Note: Procedures/Procedure/DateTime/Type/Text
should be set to Start date.

If the procedure lasted for more than one day, set an ending date. Procedures/Procedure/DateTime/Type/Text
should be set to Stop date

2008-12-15T07:00:00Z
Treated Bystring/Body/Procedures/Procedure/Source/Actor/ActorID

Note: Procedures/Procedure/Source/Actor/ActorRole/Text
should be set to Treating clinician

Tom Smith

Test Results

See an example screenshot.

This example was created from the complete ccr profile example.

Google Health UIData TypeCCR MappingExample
Namestring/Body/Results/Result/Test/Description/Text

or use a valid <Code> value instead

Glucose - Blood
Resultmeasure unit/Body/Results/Result/Test/TestResult/Value
and
/Body/Results/Result/Test/TestResult/Units/Unit		98 K/uL
Normalinteger range/Body/Results/Result/Test/NormalResult/Normal/Description/Text90 - 100
Test datedate/Body/Results/Result/Test/DateTime/ExactDateTime

Note: Results/Result/Test/DateTime/Type/Text
should be set to Collection start date

2007-02-21T07:00:00Z
Ordered Bystring/Body/Results/Result/Test/Source/Actor/ActorID

Note: Results/Result/Test/Source/Actor/ActorRole/Text
should be set to Ordering clinician

Jane Smith

Age, sex, height (Demographics)

Note: Demographic information will only be reconciled into a user's profile if they are currently empty. For example, sending a DateOfBirth will not change or update the user's birthday if they've already filled in that information in their profile.

Google Health UIData TypeCCR MappingExample
Sexstring/Actors/Actor/Person/Gender/TextMale
Date of birthdate/Actors/Actor/Person/DateOfBirth/ExactDateTime1972-03-10T07:00:00Z