Integration Guide for
Data Originators of CCR Documents
Version 1.0
Page 2
Revision History
Date Version Description Author
October 29, 2010 0.1 Draft Initial Draft J. Terrien
Page 3
Table of Contents
1.
ABOUT THIS IMPLEMENTATION GUIDE... 4
1.1 Purpose ... 4
1.2 Audience ... 4
1.3 Related Documentation ... 4
2.
SOLUTION OVERVIEW ... 5
3.
CONNECTIVITY AND SECURITY ... 6
4.
CCR REQUIREMENTS ... 7
4.1 Standards ... 7
4.2 CCR Object Types Supported ... 7
4.3 Structures ... 7
4.4 Technology Assumptions ... 11
5.
DATA REQUIREMENTS ... 12
5.1 Allergy Mapping to Portlet ... 12
5.2 Medication Mapping to Portlet ... 13
6.
ERROR HANDLING ... 15
7.
OTHER REQUIREMENTS ... 17
APPENDIX A: SAMPLE PORTLET DISPLAY ALLERGIES ... 18
APPENDIX B: SAMPLE PORTLET DISPLAY MEDICATIONS ... 19
Page 4
1. ABOUT THIS IMPLEMENTATION GUIDE
1.1 Purpose
The purpose of this document is to provide a guide to Covisint’s web service interface for data originators who wish to implement real-time exchange of the ASTM Continuity of Care Record (CCR) Standard (ASTM E2369-05)
.
1.2 Audience
This document is intended for application developers and implementers of standards-based, interoperable healthcare information systems. Implementers will require access to the ASTM E 2369 – 05 Standard and should have knowledge of XML.
1.3 Related Documentation
1.3.1 Covisint Guides
• Service Provider Master Patient Index (MPI) Transaction Specification • Service Provider Patient Sync Transaction Specification
1.3.2 Industry Documentation
• ASTM - Designation: E 2369 – 05 Standard Specification for Continuity of Care
Page 5
2. SOLUTION OVERVIEW
The CCR service retrieves clinical data real-time from a data originator and provides it to a user at the patient’s point of care. A user can access this service from a community or provider-office portal. In either case, upon receiving the user’s request, Covisint
exchangelink will invoke a web service to send an HTTP XML request to data originators, and expects to receive a synchronousASTM CCR document on the web service response.
Patient identity is critical for successful data retrieval. There are two different models that can be used for patient identification based on whether the environment is a health exchange community integration (Refer to MPI specification for more details) or a provider-office integration (Refer to Patient Synchronization specification for more specific details).
Community integration model
The community integration model is based on the existence of a community Master Patient Index (MPI). The data originator must provide a patient identity feed to the community MPI containing demographics and unique local patient identifiers. Subsequently, when Covisint exchangelink requests a CCR from the data originator, the request will contain the patient identifier that was previously supplied on the MPI patient identity feed.
Provider-office integration model
In the provider office integration model, the data originator is integrated with the patient identity source (e.g. office PMS) through Covisint’s Patient Synchronization service. In that case the query contains the local provider’s patient identifier and demographics from the office PMS, and the data originator is responsible for cross walking that identifier to its own internal patient identifier via the patient synchronization.
Page 6
3. Connectivity and Security
Covisint supports the following connectivity and security options for its CCR service: • HTTPs Post, with or without basic authentication
Page 7
4. CCR REQUIREMENTS
4.1 Standards
ASTM : E 2369 – 05 Standard Specification for Continuity of Care Record (CCR) XML schema
4.2 CCR Object Types Supported 4.2.1 Alert Type = “Allergy”
4.2.2 Product/Medication – Type = “Medication”
4.3 Structures
4.3.1 Request HTTPs Post
Parameters
Source ID: Covisint Identifier
Page 8
4.3.2 CCR – General Structure
Page 9
Page 10
Page 11
4.4 Technology Assumptions
All requests will be synchronous real-time, containing a single patient inquiry.
Covisint’s CCR service can accept and render the ASTM CCR response for display to portal users. However, if a data originator has specific requirements for displaying the information that varies from Covisint’s standard portal presentation, then custom mapping will be required. Custom mapping is outside the scope of this document.
The retrieval of a CCR from a data originator (e.g. partner application) is dependent upon the application using the Covisint patient synchronization (Patient-Sync) functionality to
synchronize patient records between the application and the Covisint platform, or the application providing a patient identity feed to Covisint for a community MPI. Depending on the model that applies to your application, key patient and/or practice values will be provided in the query message as follows:
If your application is using the patient sync model that synchronizes patient records with provider practices, then the practice identifier and associated patient id will be contained in the request and will be used by your application to retrieve the requested artifact.
• Practice ID – Identifier of the provider practice in the Covisint platform that maps directly to a provider practice in your application.
• Patient ID – The Patient identifier is used in patient synchronization to create or update patient records in your application.
If your organization provides a patient identity feed to Covisint’s MPI services, then the request will contain the patient identifier provided by your organization on the patient identity MPI feed.
• Patient ID – The Patient identifier used in MPI update to create or update patient records on the Covisint platform.
Page 12
5. DATA REQUIREMENTS
5.1 Allergy Mapping to PortletPortlet Column CCR Element Description
All CCR elements begin with the root element of <CCRDocumentObjectID>
Allergy Module (Portlet level)
<Alert>
<Type>
<Text>Allergy</Text> </Type>
Identifies the Alert (Allergy/Drug Sensitivity Module of the CCR/CCD
Valid content is:
Allergy Adverse Reaction Ignore: Reaction Alert Allergy <Agent> <Products> <Product> <Descripton> <Text>Penicillin</Text>…
</Description> </Product> </Product> </Products> </Agent> Reaction <<Reaction> <Description>…
<Attribute>Reaction</Attribute> <Value>Hives</Value>… </Description>
Reaction contains the severity value
Severity <<Reaction>
<Description>… </Description>
<severity>
<Attribute>Severity</Attribute> <Value>Life Threatening</Value>… </severity>… </Reaction> Defines the <Severity> of the <Reaction> Valid values: Minimal, Mild, Moderate, Severe, Life Threatening, Critical. Status <Status> <Text>Active</Text> </Status> Valid entries: Active Prior History No Longer Active
Page 13
5.2 Medication Mapping to Portlet
The medication status values in the ASTM standard are: Active, On Hold, Prior History and No longer Active. Many e-Prescribing Application Providers have custom status values which are outside the scope of this document. If this is the case, these status values need to be evaluated and mapped to the active state.
Status Definition Active
Active Active Medication for the patient Yes
On Hold Medication is prescribed but currently on hold for
the patient
No
Prior History Patient has taken medication for a period No
No Longer Active Patient has taken medication but is no longer
actively taking medication
No
Portlet Column CCR Element Comments
All CCR elements begin with the root element of <CCRDocumentObjectID> Medication Module (Portlet level) <Medication>… <Type> <Text>Medication</text> </Type> Valid: Medication
Other values such as Immunization, Disposable, Supplies should be ignored Medication <Product> <ProductName> <Text>Atenolol</Text> Strength <Strength> <Value>50</Value> <Units> <Unit>MG</Unit> </Units> </Strength>
Value & units display together
Drug Form <Dose>
<Value></Value> <Units>
<Unit>TABS</Unit> </Units>
</Dose>
Patient Instructions <Directions> <Direction> <Description>
<Text>TAKE 1 TABLET DAILY.</Text> </Description>
Quantity Dispensed <Quantity>
<Value>30.00</Value> <Units>
<Unit>Tab</Unit> <Code>TABS</Code>
Page 14
Portlet Column CCR Element Comments
</Units> </Quantity>
Days Supply Not available Integer 0-999
Refills remaining <Refills> <Refill>
<Number>12</Number> </Refill>
</Refills>
Integer 0-99
Fill Date Not available Format
mm/dd/yyyy Prescriber Name <Actor>
<ActorID>Person.2ebe52df-a421-4067-9044-0cbd7147cc0e</ActorID> <ActorRole> <Text>Prescribed User</Text> </ActorRole> </Actor> Lastname, Firstname
Dispensing Pharmacy Not available
Status <Status>
<Text>Active</Text> </Status>
Used to filter entries for portlet
Page 15
6. ERROR HANDLING
This discussion outlines the most common types of errors and is not necessarily all inclusive of every error that may be encountered during processing. This section is not intended to address error reporting, resolution or any other service from an operations perspective since each client and/or data originator establishes these processes or SLAs as part of their contractual agreement with Covisint.
Errors between Covisint and a data originator using the interface described in this implementation guide may fall into these areas:
Data originator fails to respond:
If a data originator fails to respond to the synchronous request within the configured time limit, then an exception will be returned by Covisint to the client indicating the data originator failed to respond. It is the responsibility of the client to interpret the exception and provide the end user with an
appropriate informational message.
The amount of time that the request will wait for a response is determined by Covisint, to ensure a consistent user experience.
Transport level exception returned by data originator
If a data originator returns a transport level error, (e.g. HTTPs 500) then an exception will be returned by Covisint to the client. It is the responsibility of the client to interpret the exception and provide the end user with an appropriate informational message.
Application level exception returned by data originator
If a data originator returns an application level error (i.e. ERROR transaction), then the error will be returned by Covisint to the client. It is the responsibility of the client to interpret the application error and provide the end user with an appropriate informational message.
Non-compliant response returned by data originator
If the data originator returns a response that does not comply with the expected standard interface defined in this Implementation Guide, then the response will be rejected. It will not be returned to the client. The client will instead receive a general exception error from Covisint.
In all cases, the Service Level Agreement (SLA) between Covisint and the data originator will determine any operational processes for responding to errors. Responses may range from no action taken, to immediate escalation for resolution. Contact your Covisint representative for information on the available options.
Rest Based (HTTP Post) Generic error response example: ---Start HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Date: Tue, 06 Oct 2009 12:16:43 GMT Content-Type: text/plain
Content-Length: 174 Connection: close
Page 16
Submitted message failed processing through the Exchange. Inbound Message ID: {tracking_id}
Outbound Message ID: {tracking_id}
SyncGuid: 091006081641625-16-7228-DTW114081N01-F8FN5W ---End
Page 17
7. OTHER REQUIREMENTS
Accuracy & CompletenessWhen processing transaction from a data originator, Covisint does not inspect and/or translate any incoming data. Content is displayed as provided and should comply with specifications contained in this document. If there are issues with data displayed, display formats and/or associated codes, it is the responsibility of the data originator to address these content issues.
If a data originator should need custom mapping, this functionality is available but is not considered part of the standard implementation activities
Audit
Covisint only audits that transactions happened within the Covisint environment; it does not log the content of those transactions. If a data source has other business requirements to log and audit the content of transactional flow, the data source must provide that capability.
Data Retention
Data that is retrieved by Covisint exchangelink using this interface is not persisted within the Covisint environment.
Page 18
Page 19
Page 20
Appendix C: Example CCR Response
<?xml version="1.0"?> <tns1:GetPatientResult> <tns1:Status>SUCCESS</tns1:Status> <tns1:Patient> <tns1:PatientID> <tns1:Value>afee4322-a53a-4474-82ef-3e1c96800354</tns1:Value> <tns1:Type>GUID</tns1:Type> </tns1:PatientID> <tns1:PatientGUID>afee4322-a53a-4474-82ef-3e1c96800354</tns1:PatientGUID> <tns1:MRN>Cookie</tns1:MRN> <tns1:LicenseID>617ba90e-9a14-442d-9747-3c3783bf9098</tns1:LicenseID> <tns1:FirstName>Cookie</tns1:FirstName> <tns1:LastName>Monster</tns1:LastName> <tns1:MiddleInitial> </tns1:MiddleInitial><tns1:Address1>125 Oatmeal Street</tns1:Address1> <tns1:Address2></tns1:Address2> <tns1:City>Raleigh</tns1:City> <tns1:State>NC</tns1:State> <tns1:ZIPCode>27615</tns1:ZIPCode> <tns1:Phone></tns1:Phone> <tns1:Gender>M</tns1:Gender> <tns1:DateOfBirth>2000-01-01T00:00:00</tns1:DateOfBirth> <tns1:SSN></tns1:SSN> <tns1:Email></tns1:Email> <tns1:CCR> <ContinuityOfCareRecord xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:astm-org:CCR"> <CCRDocumentObjectID>1.3.6.1.4.1.22812.1.00000000000000000001.</CCRDocumentObjectID> <Language> <Text>English</Text> </Language> <Version>V1.0</Version> <DateTime> <Type>
<Text>CCR Creation DateTime</Text> </Type> <ExactDateTime>2009-10-20T115955Z</ExactDateTime> </DateTime> <Patient> <ActorID>Patient.afee4322-a53a-4474-82ef-3e1c96800354</ActorID> </Patient> <From> <ActorLink> <ActorID> Person.</ActorID> <ActorRole>
Page 21 <Text>Provider</Text> </ActorRole> </ActorLink> <ActorLink> <ActorID>Site</ActorID> <ActorRole> <Text>Organization</Text> </ActorRole> </ActorLink> <ActorLink> <ActorID>ePrescribe</ActorID> <ActorRole> <Text>InformationSystem</Text> </ActorRole> </ActorLink> </From> <To> <ActorLink> <ActorID>Patient.afee4322-a53a-4474-82ef-3e1c96800354</ActorID> <ActorRole> <Text>Patient</Text> </ActorRole> </ActorLink> </To> <Purpose> <Description> <Text>Patient Request</Text> </Description> </Purpose> <Body> <Problems> <Problem> <CCRDataObjectID>3da74a02-349b-4dd6-918d-34b3668cceb0</CCRDataObjectID> <DateTime> <Type> <Text>Onset</Text> </Type> <ApproximateDateTime> <Text>2009-10-15T00:00:00Z</Text> </ApproximateDateTime> </DateTime> <IDs> <ID>3da74a02-349b-4dd6-918d-34b3668cceb0</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs> <Type> <Text>Diagnosis</Text>
Page 22 </Type> <Description>
<Text>STREP SORE THROAT</Text> <Code> <Value>034.0</Value> <CodingSystem>ICD9-CM</CodingSystem> </Code> </Description> <Status> <Text>Active</Text> </Status> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </Problem> </Problems> <Alerts> <Alert> <CCRDataObjectID>1916d938-9720-4207-a4a5-06980fe67e83</CCRDataObjectID> <DateTime> <Type> <Text>Start Date</Text> </Type> <ExactDateTime>2009-10-15T00:00:00Z</ExactDateTime> </DateTime> <IDs> <ID>1916d938-9720-4207-a4a5-06980fe67e83</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs> <Type> <Text>Allergy</Text> </Type> <Description> <Text>Dilantin - Oral</Text> </Description> <Status> <Text>Active</Text> </Status> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> <Source> <Actor>
Page 23 <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Created User</Text> </ActorRole> </Actor> </Source> <Source> <Actor> <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Updated User</Text> </ActorRole> </Actor> </Source> <Agent> <Products> <Product> <CCRDataObjectID>PR.1916d938-9720-4207-a4a5-06980fe67e83.1</CCRDataObjectID> <Type> <Text>Medication</Text> </Type> <Description> <Text>Dilantin - Oral</Text> <Code> <Value>006636</Value>
<CodingSystem>Medispan PAR ID</CodingSystem> </Code> </Description> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> <Product> <ProductName> <Text>Dilantin - Oral</Text> </ProductName> </Product> </Product> </Products> </Agent> <Reaction> <Description> <Text>Tachycardia</Text> </Description> </Reaction> </Alert> </Alerts> <Medications> <Medication> <CCRDataObjectID>bdfcabc0-3cb2-4545-9975-8eb5d15c4922</CCRDataObjectID>
Page 24 <DateTime> <Type> <Text>Prescription Date</Text> </Type> <ExactDateTime>2009-10-15T16:02:00Z</ExactDateTime> </DateTime> <DateTime> <Type> <Text>Expiration Date</Text> </Type> <ExactDateTime>2009-10-15T00:00:00Z</ExactDateTime> </DateTime> <IDs> <ID>bdfcabc0-3cb2-4545-9975-8eb5d15c4922</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs> <Type> <Text>Medication</Text> </Type> <Description>
<Text>Ibuprofen; three times per day ; </Text> </Description> <Status> <Text>New</Text> </Status> <Source> <Actor> <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Prescribed User</Text> </ActorRole> </Actor> </Source> <Source> <Actor> <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Created User</Text> </ActorRole> </Actor> </Source> <Source> <Actor> <ActorID>ePrescribe</ActorID> <ActorRole> <Text>Source System</Text> </ActorRole>
Page 25 </Actor> </Source> <Product> <ProductName> <Text>Ibuprofen</Text> <Code> <Value>40986001074</Value> <CodingSystem>NDC</CodingSystem> </Code> <Code> <Value>027909</Value>
<CodingSystem>Medispan PAR ID</CodingSystem> </Code> <Code> <Value>R</Value> <CodingSystem>Transmission Method</CodingSystem> </Code> </ProductName> <Strength> <Value>200</Value> <Units> <Unit>MG</Unit> </Units> </Strength> <Form> <Text></Text> </Form> </Product> <Quantity> <Value>0.00</Value> <Units> <Unit></Unit> <Code>Cap</Code> </Units> </Quantity> <Directions> <Direction> <Description>
<Text>three times per day</Text> </Description> <Dose> <Value></Value> <Units> <Unit>Cap</Unit> </Units> </Dose> <Route> <Text>Oral</Text> </Route> <Duration> <Value>0</Value>
Page 26 <Units> <Unit>Days</Unit> </Units> </Duration> </Direction> </Directions> <Refills> <Refill> <Number>0</Number> </Refill> </Refills> </Medication> <Medication> <CCRDataObjectID>3594f603-4d76-4392-a1dc-e48fa385b57d</CCRDataObjectID> <DateTime> <Type> <Text>Prescription Date</Text> </Type> <ExactDateTime>2009-10-15T14:20:00Z</ExactDateTime> </DateTime> <DateTime> <Type> <Text>Expiration Date</Text> </Type> <ExactDateTime>2009-10-15T00:00:00Z</ExactDateTime> </DateTime> <IDs> <ID>3594f603-4d76-4392-a1dc-e48fa385b57d</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs> <Type> <Text>Medication</Text> </Type> <Description>
<Text>Prevacid; once per day ; </Text> </Description> <Status> <Text>New</Text> </Status> <Source> <Actor> <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Prescribed User</Text> </ActorRole> </Actor> </Source>
Page 27 <Source> <Actor> <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Created User</Text> </ActorRole> </Actor> </Source> <Source> <Actor> <ActorID>ePrescribe</ActorID> <ActorRole> <Text>Source System</Text> </ActorRole> </Actor> </Source> <Product> <ProductName> <Text>Prevacid</Text> <Code> <Value>64764054119</Value> <CodingSystem>NDC</CodingSystem> </Code> <Code> <Value>040382</Value>
<CodingSystem>Medispan PAR ID</CodingSystem> </Code> <Code> <Value>R</Value> <CodingSystem>Transmission Method</CodingSystem> </Code> </ProductName> <Strength> <Value>15</Value> <Units> <Unit>MG</Unit> </Units> </Strength> <Form> <Text>Cap</Text> </Form> </Product> <Quantity> <Value>0.00</Value> <Units> <Unit>Cap</Unit> <Code>Caps</Code> </Units> </Quantity> <Directions> <Direction>
Page 28
<Description>
<Text>once per day</Text> </Description> <Dose> <Value></Value> <Units> <Unit>Caps</Unit> </Units> </Dose> <Route> <Text>Oral</Text> </Route> <Duration> <Value>0</Value> <Units> <Unit>Days</Unit> </Units> </Duration> </Direction> </Directions> <Refills> <Refill> <Number>0</Number> </Refill> </Refills> </Medication> <Medication> <CCRDataObjectID>ce16e74f-ceea-4dd9-8e55-92b915451f35</CCRDataObjectID> <DateTime> <Type> <Text>Prescription Date</Text> </Type> <ExactDateTime>2009-10-15T00:00:00Z</ExactDateTime> </DateTime> <DateTime> <Type> <Text>Expiration Date</Text> </Type> <ExactDateTime>2009-10-20T00:00:00Z</ExactDateTime> </DateTime> <IDs> <ID>ce16e74f-ceea-4dd9-8e55-92b915451f35</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs> <Type> <Text>Medication</Text> </Type>
Page 29 <Description>
<Text>Zithromax Z-Pak; TAKE 2 TABLETS ON DAY 1 THEN TAKE 1 TABLET A DAY FOR 4 DAYS. ; </Text> </Description> <Status> <Text>New</Text> </Status> <Source> <Actor> <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Prescribed User</Text> </ActorRole> </Actor> </Source> <Source> <Actor> <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Authorized User</Text> </ActorRole> </Actor> </Source> <Source> <Actor> <ActorID>Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorID> <ActorRole> <Text>Created User</Text> </ActorRole> </Actor> </Source> <Source> <Actor> <ActorID>ePrescribe</ActorID> <ActorRole> <Text>Source System</Text> </ActorRole> </Actor> </Source> <Product> <ProductName> <Text>Zithromax Z-Pak</Text> <Code> <Value>00069306075</Value> <CodingSystem>NDC</CodingSystem> </Code> <Code> <Value>070227</Value>
<CodingSystem>Medispan PAR ID</CodingSystem> </Code>
Page 30 <Value>S</Value> <CodingSystem>Transmission Method</CodingSystem> </Code> </ProductName> <Strength> <Value>250</Value> <Units> <Unit>MG</Unit> </Units> </Strength> <Form> <Text>Tab</Text> </Form> </Product> <Quantity> <Value>1.00</Value> <Units> <Unit>Tab</Unit> <Code>TABS</Code> </Units> </Quantity> <Directions> <Direction> <Description>
<Text>TAKE 2 TABLETS ON DAY 1 THEN TAKE 1 TABLET A DAY FOR 4 DAYS.</Text> </Description> <Dose> <Value></Value> <Units> <Unit>TABS</Unit> </Units> </Dose> <Route> <Text>Oral</Text> </Route> <Frequency> <Value>OTHER</Value> </Frequency> <Duration> <Value>5</Value> <Units> <Unit>Days</Unit> </Units> </Duration> </Direction> </Directions> <Refills> <Refill> <Number>0</Number> </Refill> </Refills>
Page 31 </Medication> </Medications> </Body> <Actors> <Actor> <ActorObjectID>Patient.afee4322-a53a-4474-82ef-3e1c96800354</ActorObjectID> <Person> <Name> <CurrentName> <Given>Cookie</Given> <Family>Monster</Family> </CurrentName> <DisplayName>CookieMonster</DisplayName> </Name> <DateOfBirth> <ApproximateDateTime> <Text>01/01/2000</Text> </ApproximateDateTime> </DateOfBirth> <Gender> <Text>Male</Text> </Gender> </Person> <IDs> <Type> <Text>Patient ID</Text> </Type> <ID></ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> <ActorRole> <Text>ERX</Text> </ActorRole> </Actor> </Source> </IDs> <Address> <Type> <Text>Mail</Text> </Type>
<Line1>125 Oatmeal Street</Line1> <City>Raleigh</City> <State>NC</State> <PostalCode>27615</PostalCode> </Address> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source>
Page 32 </Actor> <Actor>
<ActorObjectID>Site</ActorObjectID> <Organization>
<Name>AMA Test Site</Name> </Organization>
<Address> <Type>
<Text>Mail</Text> </Type>
<Line1>4 AMA Way</Line1> <City>Hollywood</City> <State>CA</State> <PostalCode>90027</PostalCode> </Address> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </Actor> <Actor> <ActorObjectID>ePrescribe</ActorObjectID> <InformationSystem>
<Name>ePrescribe by Allscripts, LLC.</Name> <Type>ERX</Type> <Version>1.5.0</Version> </InformationSystem> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </Actor> <Actor> <ActorObjectID>Medication.ce16e74f-ceea-4dd9-8e55-92b915451f35</ActorObjectID> <InformationSystem> <Name>CVS/PHARMACY #8081</Name> <Type>Pharmacy</Type> </InformationSystem> <IDs> <Type> <Text>NABP</Text> </Type> <ID>2342739</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs>
Page 33 <Address> <Type>
<Text>Mail</Text> </Type>
<Line1>17120 KERCHEVAL AVE</Line1> <Line2></Line2> <City>GROSSE POINTE</City> <State>MI</State> <PostalCode>48230</PostalCode> </Address> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </Actor> <Actor> <ActorObjectID> Person.703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ActorObjectID> <Person> <Name> <CurrentName> <Given>Katherine</Given> <Family>Ernhart</Family> </CurrentName> </Name> </Person> <IDs> <Type> <Text>User ID</Text> </Type> <ID>703dbf92-8a38-48b6-8af6-ccfc182a2eeb</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs> <IDs> <Type> <Text>User Name</Text> </Type> <ID>kye_ama</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs> <IDs> <Type>
Page 34 <Text>User Type</Text> </Type> <ID>Provider</ID> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </IDs> <Address> <Type> <Text>Mail</Text> </Type> </Address> <Source> <Actor> <ActorID>ePrescribe</ActorID> </Actor> </Source> </Actor> </Actors> </ContinuityOfCareRecord></tns1:CCR> <tns1:Status>ACTIVE</tns1:Status> </tns1:Patient>
