Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents...

41
Wolf EMR Community Information Integration (CII) and Central Patient Attachment Registry (CPAR) Guide

Transcript of Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents...

Page 1: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Wolf EMR

Community Information Integration (CII) andCentral Patient Attachment Registry(CPAR) Guide

Page 2: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Revised December 9, 2019, version 2019.4

Wolf EMR software and related products and services are owned by TELUS. Wolf EMR andTELUS Health are trademarks of TELUS.

The patients, physicians and circumstances depicted within this manual are fictitious. Anyresemblance of any sample data or screenshots to any actual person, whether living or dead,is purely coincidental and unintentional.

Page 3: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

3

Table of contents

Alberta Health Community Information Integration (CII) 4Community Information Integration (CII) 4Central Patient Attachment Registry (CPAR) 5

Checklist to configure Wolf EMR for CII/CPAR integration 6Sending only encounter data (only CII) 6Sending only consult reports (specialists) (only CII) 7Sending encounter and panel data (CII and CPAR) 8Enabling EMR integration CII 9Enabling EMR integration with CPAR 11

Sending your consult reports to Alberta Netcare via CII (Specialists) 14Assigning document types to consult report SMART forms 16

Information sent to Alberta Netcare through CII 17Patient demographics 18General encounter information and measured observations 21Medical problems 27Surgical procedures 28Allergies 29Immunizations 30Referrals (consult requests) 32Provider information 34Location information 37

Preventing patient data from being sent to Alberta Netcare 39CII FAQs 40

How will CII integration change my workflow? 40What happens if I delete or modify an encounter in my EMR? 40What happens if I merge patient charts in my EMR? 41What happens if I deactivate or delete a patient chart in my EMR? 41What privacy and security protections are in place for the data being shared? 41

Page 4: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

4

Alberta Health Community Information Integration (CII)

Wolf EMR supports the sending of patient data to Alberta Netcare for the Community InformationIntegration (CII) and Central Patient Attachment Registry (CPAR) integration projects.

To participate in these programs, your clinic and at least one provider within your clinic must registerwith Alberta Netcare (see http://www.albertanetcare.ca/learningcentre/CII.htm).

Once you are registered with Alberta Netcare, you must configure your Wolf EMR to submit patientdata (see "Checklist to configure Wolf EMR for CII/CPAR integration" on page 6).

You can register to participate in only CII or both CII and CPAR.

Community Information Integration (CII)

If you register for CII, your basic EMR encounter information becomes available in Alberta Netcare aspart of a comprehensive patient electronic health record (EHR).

The information displays in Alberta Netcare in one of two ways:

n Community Encounter digest (CED) reports, which offer a snapshot of patient care over the past12 months (see "Information sent to Alberta Netcare through CII" on page 17)

n Specialist Consult reports, which outline assessments and recommended treatment plans for apatient, in PDF format

Note: Any information sent to Alberta Netcare for CII/CPAR becomes available on theAlberta Netcare site the next day.

The primary goal of CII/CPAR is to improve Albertans’ continuity of care across the health systemthrough better access to primary care and community health information. The information is alsoused to support quality improvement efforts and health system planning.

For more information about CII/CPAR and how to register, see the Alberta Netcare website:http://www.albertanetcare.ca/learningcentre/CII.htm.

Page 5: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Central Patient Attachment Registry (CPAR)

CPAR is a centralized provincial database that captures the attachment of primary care physiciansand nurse practitioners and their paneled patients. It is a key technical enabler for better continuity ofcare for Albertans by facilitating improved relational and informational continuity and data for healthcare planning. CPAR:

n Identifies relationships between patients and their primary provider

n Allows for family physicians to identify and coordinate when patients are on multiple panels andtherefore, will enable validated patient-family physicians information to be available on AlbertaNetcare Portal

n Provides an opportunity to confirm roles and responsibilities in care provision

n Supports notification of primary providers when their patient has a hospitalization or ER visit

If your clinic registers for CPAR integration, your providers’ primary patient panel information will beextracted from your EMR and sent to CPAR on a regular basis. Only the following basic patientinformation is included in the data extract:

Patient first, last, and preferred name Province from which the patient is insured

Gender Dave on which the demographics were last validated

Date of birth Date of last visit

Provincial health number

For more information about CPAR, see the Alberta Medical Association's Accelerating ChangeTransformation Team website: https://actt.albertadoctors.org/cii-cpar.

HowCPAR determines which patients are in a provider’s panel

For CPAR, a patient is considered to be included in a provider’s panel, only if the following criteria aremet:

n InPatient Maintenance, the patient’s Primary Service Provider is selected and the primaryprovider is set up for CPAR integration

n The patient’s provincial health number (PHN) and gender are recorded

n The patient is assigned a "paneled" patient status (see "Setting patient status options to bepaneled for CPAR" on page 13)

5

Alberta Health Community Information Integration (CII)

Page 6: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Checklist to configureWolf EMR for CII/CPAR integration

Depending on what and what data you will submit, you must perform the following steps to sendyour patient data to Alberta Netcare

In all instances, if a new provider joins your clinic once it's already configured, you must contactAlberta Netcare to register the new provider (seehttp://www.albertanetcare.ca/learningcentre/CII.htm).

Sending only encounter data (onlyCII)

If you send encounter data to Alberta Netcare via the Community Information Integration (CII) project,follow this process:

1. Register your clinic and at least one provider with Alberta Netcare (seehttp://www.albertanetcare.ca/learningcentre/CII.htm).

6

Alberta Health Community Information Integration (CII)

Page 7: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

2. Accept the terms and conditions for TELUS EMR Mobile (see "Managing mobile access" in theWolf EMR help).

Note: Even if you do not use TELUS EMR Mobile, you must accept the terms andconditions in Wolf EMRMaintenance tab > ManageMobile Settings. The termsand conditions apply to CII/CPAR as well. If you already use TELUS EMR Mobile,you do not need to accept the terms and conditions again for CII/CPAR.

3. Configure Wolf EMR to enable sending patient encounter information to Alberta Netcare (see"Enabling EMR integration CII" on page 9.

4. Understand how and what information is sent to Alberta Netcare (see "Information sent to AlbertaNetcare through CII" on page 17).

5. Understand the process to send an encounter/visit.

6. Understand how to prevent data from being sent (see "Preventing patient data from being sent toAlberta Netcare" on page 39).

Sending only consult reports (specialists) (onlyCII)

If you are a specialist sending only consult reports to Alberta Netcare via the Community InformationIntegration (CII) project, follow this process:

1. Register your clinic and at least one provider with Alberta Netcare (seehttp://www.albertanetcare.ca/learningcentre/CII.htm).

2. Accept the terms and conditions for TELUS EMR Mobile (see "Managing mobile access" in theWolf EMR help).

Note: Even if you do not use TELUS EMR Mobile, you must accept the terms andconditions in Wolf EMRMaintenance tab > ManageMobile Settings. The termsand conditions apply to CII/CPAR as well. If you already use TELUS EMR Mobile,you do not need to accept the terms and conditions again for CII/CPAR.

3. Configure Wolf EMR to enable sending consult reports to Alberta Netcare (see "Enabling EMRintegration CII" on page 9.

4. Configure your consult report SMART forms to have aDocument Type ofConsult Report (see"Assigning document types to consult report SMART forms" on page 16).

7

Alberta Health Community Information Integration (CII)

Page 8: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

5. Understand what information is sent to Alberta Netcare (see "Information sent to Alberta Netcarethrough CII" on page 17).

6. Understand how to prevent data from being sent (see "Preventing patient data from being sent toAlberta Netcare" on page 39).

7. Follow the workflow to send your consult reports (see "Sending your consult reports to AlbertaNetcare via CII (Specialists)" on page 14).

Sending encounter and panel data (CII andCPAR)

If you send both patient encounter and panel data to Alberta Netcare, follow this process:

1. Register your clinic and at least one provider with Alberta Netcare (seehttp://www.albertanetcare.ca/learningcentre/CII.htm).

2. Accept the terms and conditions for TELUS EMR Mobile (see "Managing mobile access" in theWolf EMR help).

Note: Even if you do not use TELUS EMR Mobile, you must accept the terms andconditions in Wolf EMRMaintenance tab > ManageMobile Settings. The termsand conditions apply to CII/CPAR as well. If you already use TELUS EMR Mobile,you do not need to accept the terms and conditions again for CII/CPAR.

3. Configure Wolf EMR to send patient panel information to Alberta Netcare (see "Enabling EMRintegration with CPAR" on page 11).

4. Configure which patient statuses are sent to Alberta Netcare (see "Setting patient status optionsto be paneled for CPAR" on page 13).

5. Understand how and what information is sent to Alberta Netcare (see "Information sent to AlbertaNetcare through CII" on page 17).

6. Understand how to prevent data from being sent (see "Preventing patient data from being sent toAlberta Netcare" on page 39).

Important :TELUS Health creates the following EMR user accounts in your Wolf EMR system.These are required to properly access and send patient data to the Netcare CII andCPAR projects. Do not alter or delete these user accounts, as doing so will preventsending the information.

8

Alberta Health Community Information Integration (CII)

Page 9: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

n Integration Engine User ( IEuser) with an Administrator role

n Data Integration (dintegration) with an Administrator role

EnablingEMR integrationCII

If you have administrative privileges in Wolf EMR and your clinic is registered for Alberta Health CII,you can enable or disable sending of patient encounter information to Alberta Netcare.

Also, if you are part of a specialist clinic, when you configure this feature, you can choose to have anyconsult reports created by specialists sent to Alberta Netcare. To do this, you must also configureyour consult report SMART forms to have aDocument Type set to Consult Report. See "Assigningdocument types to consult report SMART forms" on page 16.

Steps

1. On the Wolf EMR home page, clickConfiguration . TheConfiguration window opens.

2. Click theRuntimeConfiguration tab.

3. At the bottom right of the window, in theOutbound Interface section, select theEnableEncounter + Chart Summary check box.

9

Alberta Health Community Information Integration (CII)

Page 10: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Note: If you do not see theEnable Encounter + Chart Summary check box,contact the Wolf EMR support team to have the feature enabled on your system.

4. ClickSave .

10

Alberta Health Community Information Integration (CII)

Page 11: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

EnablingEMR integrationwithCPAR

If you have administrative privileges in Wolf EMR and at least one provider is registered for AlbertaNetcare CPAR integration, you can enable or disable sending of provider patient panel information toAlberta Netcare for each provider.

Steps

1. On the Wolf EMR home page, clickConfiguration . TheConfiguration window opens.

2. Click theView > Physicians / Service Providers > Office Service Providers. ThePhysicians /Service Providers in Clinicwindow opens.

3. In theOffice Service Provider list, choose a provider.

4. In theOther Data tab, chooseAssign Panel Number(s).

5. In theCPAR Panel Numberwindow, in the Location list, choose the clinic location for which youwant to set the provider’s panel information.

11

Alberta Health Community Information Integration (CII)

Page 12: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

6. In thePanel Number field, type the provider’s panel number (provided by Alberta Health).

Note: In cases where two providers share the same panel of patients, thoseproviders will have the same panel number.

7. In theAHFacility number field, type the provider’s facility ID (provided by Alberta Health).

Note:TheAHFacility number is typically the same for all providers who work out of thesame clinic location.

You can find this ID in Wolf EMR inConfiguration > View > Physician/ServiceProvider > Office Service Providers > Billing tab, within theDefault ServiceLocation area.

8. Beside theAHFacility number, click .

9. If your clinic has multiple locations that share the same EMR database, for each location theprovider works out of, repeat step 5 to 8.

10. ClickClose.

11. For each provider who is participating in CPAR, repeat step 3 to 10.

12

Alberta Health Community Information Integration (CII)

Page 13: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Setting patient status options to be paneled for CPAR

If your clinic is set up to send provider patient panel information to Alberta Netcare through CPAR, youmust define which patient status options indicate that patients are paneled with a provider at yourclinic.

Steps

1. On the Wolf EMR home page, clickConfiguration . TheConfiguration window opens.

2. ChooseView > Patient DataCodes > Patient Status. ThePatient Status Maintenancewindowopens.

3. Choose the patient status, and then select thePaneled check box.

4. ClickSave .

5. For every status that should be included in the panel, repeat step 3 to Step 4.

13

Alberta Health Community Information Integration (CII)

Page 14: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Sending your consult reports to Alberta Netcare via CII (Specialists)

If you are a specialist, and you write your encounter notes in the form of a consult letter/report, thereport can be sent to Alberta Netcare as a single PDF document. This way, Alberta Netcare users caneasily access your consult reports.

You must have subscribed with Alberta Health to have your consult reports sent to Alberta Netcare.

Your letters are sent to Alberta Netcare only if you use a SMART form letter template that has aDocument Type ofConsult Report (see "Assigning document types to consult report SMARTforms" on page 16) and if the SMART form is linked to the appointment or produced on the date ofthe appointment.

Tip:If you do NOT want a document to be sent to Alberta Netcare (for example, if a patientrequests that their health information remain private), ensure that the SMART formtemplate you are using does NOT have a document type ofConsult Report by doingone of the following. Only documents with the typeConsult Report are sent to AlbertaNetcare.

n In the document properties, change theDocument Type from Consult Report to"none" or to another type. You must do this within 5 minutes of saving the documentor before saving the document.

n Create and use a consult letter template that doesn’t have the document type ofConsult Report assigned to it.

For example, create one consult letter template WITH a document type ofConsultReport and name it to include Netcare it its name (such as Consult letter - Netcare)and another one without a document type or with a different document type for whenyou don't want to send the report to Netcare. See "Assigning document types toconsult report SMART forms" on page 16.

The letter is also saved in theDocuments area of the patient’s chart.

Tip: If you do not want a particular consult letter to be sent to Alberta Netcare you canrestrict access to the associated visit note or chart. See "Preventing patient data frombeing sent to Alberta Netcare" on page 39.

14

Alberta Health Community Information Integration (CII)

Page 15: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Steps

1. Enter your notes using theConsult Letter Examination form. For detailed steps, see "Enteringvisit notes in the consult letter form" in the Wolf EMR help.

2. Format your letter using a SMART form letter template that has Consult Report as its documenttype.

When you sign and close the letter, as long as it uses a SMART form letter template with one ofthe above document types, it is automatically sent to Alberta Netcare. You don't need to print orfax it to be sent to Alberta Netcare.

15

Alberta Health Community Information Integration (CII)

Page 16: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Tip: Don’t know what SMART forms have the correct document type? You can viewand modify SMART form document types from the SMART forms configurationwindow. See "Assigning document types to consult report SMART forms" below.

3. Print or send your consult letter to the referring provider, as usual.

Assigningdocument types toconsult report SMART forms

If you are a specialist and you want your consult reports to be sent to Alberta Netcare as PDFdocuments, you must use a SMART form letter template that has aDocument Type ofConsultReport. For this reason, prior to your clinic being implemented with Alberta Netcare CII, you shouldset your SMART form letter templates to the correct document type.

See also "Sending your consult reports to Alberta Netcare via CII (Specialists)" on page 14 and"Preventing patient data from being sent to Alberta Netcare" on page 39.

Steps

1. From the Wolf EMRHome tab, click theMaintenance tab, and then choose one of the followingoptions:

n ConfigureMySMART Forms : To change the SMART form document type for only yourSMART forms.

n ConfigureClinic SMART Forms : To change the SMART form document type for allusers.

TheConfigureClinic SMART Forms window opens with a list of your SMART forms displayed.

2. Beside the form, in theDefault Document Type list, chooseConsult Report.

16

Alberta Health Community Information Integration (CII)

Page 17: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Information sent to Alberta Netcare throughCII

The following data from your EMR is automatically submitted to Alberta Netcare after you completeeach patient encounter (once you close and sign-off the visit note). Only data recorded during or onthe day of the encounter is sent. No historic patient medical data is sent.

Note: Some information is sent to Alberta Netcare's healthcare data repository, but isn'tdisplayed within the Alberta Netcare's Community Encounter digest (CED) reports.These elements are noted below.

Patient data is sent only if all of the following criteria are met:

1. You create a new visit note or modify/update a previous visit note (even if the visit note beingmodified was already sent to Alberta Netcare).

2. The patient’s current encounter or chart is not masked as private. See "Preventing patient datafrom being sent to Alberta Netcare" on page 39.

17

Alberta Health Community Information Integration (CII)

Page 18: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

3. The patient’s first name, date of birth and provincial health number (PHN) are recorded inPatientMaintenance.

4. The provider’s first name is recorded in thePhysicians/Service Providers in Clinicwindow.

5. You closed and signed-off the visit note (by clicking Yes when prompted to Sign and LockRecord).

Data elements sent to AlbertaNetcare

Below is a detailed list of all data elements from your EMR that are sent to Alberta Netcare in someway, where they are sent or appear, and where to find them in your EMR.

Patient demographics

Each time encounter information is sent, the following elements of the patient’s demographics aresent as well.

Data elementCEDreports

CPARHealthcaredatarepository

Location in the EMR

Patient lastname

X X Patient Maintenance (Family name)

Patient givenname

X X Patient Maintenance> Name/Addr/Phone tab >Given name

Patientpreferredname

X Patient Maintenance> Name/Addr/Phone tab >Chosen name

Patientresidencepostal code

X Patient Maintenance> Name/Addr/Phone tab >Postal code

Patientidentifier

X X Patient Maintenance> Name/Addr/Phone tab >PHN

Patientidentifierassigningauthority

X X Patient Maintenance> Name/Addr/Phone tab >Billing province

Patient dateof birth

X X Patient Maintenance> Name/Addr/Phone tab>Birthdate

18

Alberta Health Community Information Integration (CII)

Page 19: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Data elementCEDreports

CPARHealthcaredatarepository

Location in the EMR

Patientadministrativegender

X X Patient Maintenance> Name/Addr/Phone tab >Gender

ConfirmationDate

X Patient Maintenance> Name/Addr/Phone tab >Patient Data Verified

Last VisitDate

X Patient Maintenance> Other Demographics tab> Last Visit

Patient statuscode

X Patient Maintenance> Patient Status tab

Note: If no status is entered in thedemographics, a status of active issent. For deceased patients a statusof inactive along with the deceaseddate is sent.

In the following screenshots, information highlighted in red is visible in the patient’s Alberta NetcareCED report. Information in blue is sent only to the healthcare data repository.

19

Alberta Health Community Information Integration (CII)

Page 20: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Following is an example of how patient demographic information appears at the top of the CEDreport:

20

Alberta Health Community Information Integration (CII)

Page 21: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

General encounter information andmeasured observations

When your encounter information is sent to CII, your detailed visit notes are not included. Only thefollowing basic encounter information is sent or visible to other healthcare professionals who accessa patient’s Alberta Netcare CED report.

Data elementCEDreports

Healthcaredatarepository

Location in the EMR

Encounter status X A hard-coded status of "Active" is sent. If you deletean encounter, a hard-coded status of "Deleted" issent.

Encounter requestdate

X Medical summary> Current Hx tab > Encounters

Patient encounterreason

X WorkDesk > Appointments tab and AppointmentDetailwindow > Reason (if available; otherwise, theChief Complaint in the encounter note is sent)

Encounter date X Medical summary> Current Hx tab > Encounters

Encounter paymentsource

X Medical summary> Current Hx tab > Encounters >Insurer

21

Alberta Health Community Information Integration (CII)

Page 22: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Data elementCEDreports

Healthcaredatarepository

Location in the EMR

Encounter billingcode (healthservice code)

X Medical summary> Current Hx tab > Encounters >FeeCode

Observationsystolic bloodpressure

X Medical summary> Current Hx tab > Encounters >BPSystolic

Observationdiastolic bloodpressure

X Medical summary> Current Hx tab > Encounters >BPDiastolic

Observation height X Medical summary> Current Hx tab > Encounters >Height

Observation heightunit of measure

X Medical summary> Current Hx tab > Encounters >Length Units

Observation weight X Medical summary> Current Hx tab > Encounters >Weight

Observation weightunit of measure

X Medical summary> Current Hx tab > Encounters >Weight Units

Observation waistcircumference

X Medical summary> Current Hx tab > Encounters >Waist Circ

Observation waistcircumference unitof measure

X Medical summary> Current Hx tab > Encounters >Length Units

Observationencounter clinicalassessment

X Medical summary> Current Hx tab > Encounters >Assessment

Lab test nameordered

X Medical summary> Current Hx tab > Encounters >Ordered Investigations

Diagnostic imagingtest ordered

X Medical summary> Current Hx tab > Encounters >Ordered Investigations

In the following screenshots, information highlighted in red is visible in the patient’s Alberta NetcareCED report. Information in blue is sent only to the healthcare data repository.

22

Alberta Health Community Information Integration (CII)

Page 23: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

23

Alberta Health Community Information Integration (CII)

Page 24: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

24

Alberta Health Community Information Integration (CII)

Page 25: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Note: If you capture the visit diagnosis or patient vitals using any of the alternative forms,exams, or windows available in Wolf EMR (for example, the prenatal form), it is still sent toAlberta Netcare. However, only the diagnosis and vitals entered during the encounter aresent (and not historical ones).

Following is an example of how a patient’s general encounter information appears in the AlbertaNetcare CED report.

25

Alberta Health Community Information Integration (CII)

Page 26: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Following is an example of how a patient’s vitals display in the CED report:

Note: If you later edit or delete the encounter note from Wolf, it will appear in the CEDreport with a strike-through and indicate it has been retracted. See "CII FAQs" onpage 40.

26

Alberta Health Community Information Integration (CII)

Page 27: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Medical problems

If, during the encounter, you record a medical problem (such as by adding a problem to the problemlist), the problem (shown in red below) is added to theHealth Concern History area of the patient’sAlberta Netcare CED report. Only the problem’s diagnosis description displays in the report.

Data elementCEDreports

Healthcaredatarepository

Location in the EMR

Observation health concern X Medical summary> Current Hx tab >Problems > Active Problem

Observation health concerndate of onset

X Medical summary> Current Hx tab >Problems > Onset

In the following screenshot, information highlighted in red is visible in the patient’s Alberta NetcareCED report. Information in blue is sent only to the healthcare data repository.

Following is an example of how a patient’s medical problems display in the CED report.

27

Alberta Health Community Information Integration (CII)

Page 28: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Surgical procedures

If, during the encounter, you record a procedure in the patient’s medical summary, the surgicalprocedure is sent to only the healthcare data repository.

Data elementCEDreports

Healthcaredatarepository

Location in the EMR

Intervention/treatment X Medical summary> Past Hx tab > Proceduresand Surgeries

Intervention/treatmentdate

X Medical summary> Past Hx tab > Proceduresand Surgeries

In the following screenshot, information highlighted in blue is sent only to the healthcare datarepository..

28

Alberta Health Community Information Integration (CII)

Page 29: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Allergies

If, during the encounter, you record an allergy or intolerance for the patient, the allergy is added to thePossible Allergy area of the patient’s Alberta Netcare CED report. Only the offending agent (allergen)is included.

Data elementCEDreports

CPAR Location in the EMR

Observation allergy agent X Medical summary> Allergies > Allergy To

In the following screenshot, information highlighted in red is visible in the patient’s Alberta NetcareCED report.

Legacy prescriber interface

New prescriber interface

29

Alberta Health Community Information Integration (CII)

Page 30: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Following is an example of how a patient’s allergies appear in the CED report.

Immunizations

If, during the encounter, you record an immunization, the immunization is added to theImmunizations area of the patient’s Alberta Netcare CED report. Only the following information isincluded.

Data elementCEDreports

Healthcaredatarepository

Location in the EMR

Vaccine administeredname

X Medical summary> Vaccinations >Vaccine

Vaccine administered date X Medical summary> Vaccinations >Vaccination Date

30

Alberta Health Community Information Integration (CII)

Page 31: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Data elementCEDreports

Healthcaredatarepository

Location in the EMR

Vaccine administered lotnumber

X Medical summary> Vaccinations > Lot #

In the following screenshot, information highlighted in red is visible in the patient’s Alberta NetcareCED report.

Following is an example of how a patient’s immunizations appear in the CED report:

31

Alberta Health Community Information Integration (CII)

Page 32: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Referrals (consult requests)

If, during the encounter, you create a referral, or consult request (for example, by right-clicking andchoosing NewReferral), the referral is added to theReferrals area in the patient’s Alberta NetcareCED report. The following information is included as well.

Data elementCEDreports

Healthcaredatarepository

Location in the EMR

Referral service X Medical summary> Referrals tab > existing referral >Specialty

Referralrequested date

X Medical summary> Referrals tab > existing referral >Date the referral was sent

Referraloccurred date

X Medical summary> Referrals tab > existing referral >Appt Date/Time

In the following screenshot, information highlighted in red is visible in the patient’s Alberta NetcareCED report.

32

Alberta Health Community Information Integration (CII)

Page 33: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Note: The actual referral letter (consult request) you send to the specialist is not sent toNetcare.

Following is an example of how a patient’s referrals appear in the CED report.

33

Alberta Health Community Information Integration (CII)

Page 34: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Provider information

Each time encounter information is sent, the following provider information is sent as well.

Data elementCEDreports

Healthcaredatarepository

Location in the EMR

Provider lastname

X Physicians/Service Providers in Clinic> Name/Addresstab

Provider firstname

X Physicians/Service Providers in Clinic> Name/Addresstab

Provider middlename

X Physicians/Service Providers in Clinic> Name/Addresstab

Provideridentifier

X Physicians/Service Providers in Clinic> Billing tab >Practitioner Number,PayeeNumber, and college ID

Providerexpertise(specialty)

X Physicians/Service Providers in Clinic> Name/Addresstab

In the following screenshots, information highlighted in red is visible in the patient’s Alberta NetcareCED report. Information in blue is sent only to the healthcare data repository.

34

Alberta Health Community Information Integration (CII)

Page 35: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

35

Alberta Health Community Information Integration (CII)

Page 36: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Following is an example of how provider information appears in CED reports.

36

Alberta Health Community Information Integration (CII)

Page 37: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Location information

Each time encounter information is sent, the following location elements are sent as well.

Data elementCED reports

Healthcaredatarepository

Location in the EMR

Servicedeliverylocation name

X Configuration > Clinic Address/Phone tab > ClinicName

Note: If your clinic has more than onelocation, your specific location name is notused. Only the clinic or site name is used.

Servicedelivery postalcode

X Configuration > Clinic Address/Phone tab > PostalCode

In the following screenshot, information highlighted in red is visible in the patient’s Alberta NetcareCED report. Information in blue is sent only to the healthcare data repository.

37

Alberta Health Community Information Integration (CII)

Page 38: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Following is an example of how location information appears in CED reports.

38

Alberta Health Community Information Integration (CII)

Page 39: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Preventing patient data from being sent to Alberta Netcare

If a patient requests that all or part of their health information remain confidential (and is not to be sentto Alberta Netcare), you can prevent selected health information from being sent by “masking” thedata (making the data private or confidential). You use the same privacy restrictions uses to preventusers in the clinic from accessing patient data. From thePatient Maintenancewindow, chooseView> Patient DataRestrictions. Masking data may prevent other users in the clinic from accessing thepatient chart. You can mask:

n An entire patient’s chart (when adding data restrictions, choose<All> as the module to restrict)

n A section of a patient’s chart , such as problems or allergies (choose the appropriate module torestrict)

n A visit (chooseSpecific Visit Note as the module to restrict and then, from theRestrictedDataRecord list, choose the specific note to mask)

39

Alberta Health Community Information Integration (CII)

Page 40: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

Tip:For specialists, if you do NOT want a document to be sent to Alberta Netcare, ensure thatthe SMART form template you are using does NOT have a document type ofConsultReport by doing one of the following. Only documents with the typeConsult Report aresent to Alberta Netcare.

n In the document properties, change theDocument Type from Consult Report to"none" or to another type. You must do this within 5 minutes of saving the documentor before saving the document.

n Create and use a consult letter template that doesn’t have the document type ofConsult Report assigned to it.

For example, create one consult letter template WITH a document type ofConsultReport and name it to include Netcare it its name (such as Consult letter - Netcare)and another one without a document type or with a different document type for whenyou don't want to send the report to Netcare. See "Assigning document types toconsult report SMART forms" on page 16.

CII FAQs

Howwill CII integration changemyworkflow?

You do not have to change your workflow as data is transmitted automatically in the background.

When you lock a note (i.e. by “closing the door” and then choosing Yes when prompted to lock thenote), the encounter information is sent to Alberta Netcare.

What happens if I delete ormodify an encounter in myEMR?

If you modify or update an encounter in the EMR, on the Alberta Netcare CED report, the previousversion displays with a strikethrough and a new encounter is created with the updated information.

40

Alberta Health Community Information Integration (CII)

Page 41: Wolf EMR Community Information Integration (CII) and ... · 3 Tableofcontents AlbertaHealthCommunityInformationIntegration(CII) 4 CommunityInformationIntegration(CII) 4 CentralPatientAttachmentRegistry(CPAR)

If you delete an encounter in your EMR, but the encounter was already sent to Alberta Netcare, theencounter displays with a strikethrough on the Alberta Netcare CED report.

What happens if I merge patient charts in myEMR?

If you merge patient charts, any encounters sent for the previous chart are deleted, and are thenadded to the new “merged” chart.

What happens if I deactivate or delete a patient chart in myEMR?

If a patient chart is deactivated or deleted in your EMR, the information in Alberta Netcare remainsuntouched.

What privacy and security protections are in place for the data being shared?

Data is transferred directly from your EMR’s data centre to the Alberta Health data centre via adedicated web service that uses strong encryption. Data from the Alberta Health data centre thengoes to Alberta Netcare clinical repositories and to the Alberta Health analytic environment through avirtual private network (VPN) that also uses strong encryption.

The Alberta Health data centre meets high standards of data security with firewalls, intrusiondetection, antimalware systems and redundancy of power supply and hardware to ensure highavailability and data integrity.

41

Alberta Health Community Information Integration (CII)