HL7 Immunization User Group Monthly Meeting February 13, 2020 - - PowerPoint PPT Presentation

hl7 immunization user group
SMART_READER_LITE
LIVE PREVIEW

HL7 Immunization User Group Monthly Meeting February 13, 2020 - - PowerPoint PPT Presentation

HL7 Immunization User Group Monthly Meeting February 13, 2020 2:00 PM ET Agenda Welcome - Which perspective do you primarily identify yourself with? Updates SISC FHIR Five on FHIR Error Code Review Review of Guidance


slide-1
SLIDE 1

HL7 Immunization User Group

Monthly Meeting February 13, 2020 2:00 PM ET

slide-2
SLIDE 2

Agenda

  • Welcome - Which perspective do you primarily identify yourself with?
  • Updates
  • SISC
  • FHIR
  • Five on FHIR
  • Error Code Review
  • Review of Guidance
  • Implementation Demonstration
  • M&I Testing for Error Handling
  • HL7 FAQ
slide-3
SLIDE 3

SISC Update

Heather Patrick

slide-4
SLIDE 4

FHIR Update

Nathan Bunker

slide-5
SLIDE 5

FHIR Update

  • HL7 met in Sydney Australia
  • Work continues on FHIR r5
  • Pre-R5 milestone 4.2.0 released at Sydney Connetathon
  • Upcoming meetings:
  • Mar 19-13, 2020 – HIMSS20 HL7 Booth #2921 – Orlando FL
  • May 16-22, 2020 – WGM & FHIR Connectathon – San Antonio TX
  • Jun 16-18, 2020 – HL7 FHIR DevDays – Cleveland OH
  • Sep 18-25, 2020 – WGM & FHIR Connectathon – Baltimore MD
  • Jan 16-22, 2021 – WGM & FHIR Connectathon – Henderson NV
slide-6
SLIDE 6

Five on FHIR

Nathan Bunker

slide-7
SLIDE 7

Immunization Decision Support

  • Working group under HL7 Public Health (PH) Work Group
  • Meet every week, Friday 11 am ET
  • Proposals are brought to PH for discussion and approval
  • Creating an implementation guide to:
  • Provide standard integration with CDS engines
  • Create common interface for FITS to test CDS engines
  • Learn how to publish FHIR guides
  • Current guide can be found here:
  • http://build.fhir.org/ig/HL7/ImmunizationFHIRDS/index.html
slide-8
SLIDE 8

EHR Query to IIS

slide-9
SLIDE 9

IIS User Inter- face

slide-10
SLIDE 10

Public Health Function

slide-11
SLIDE 11

Progress and Next Steps

  • Project Phase 1: Healthy Child, Adolescent, and Adult
  • Ballot completed, all comments have dispositions
  • Updating the Implementation Guide
  • Will start process for publication soon
  • Looking to demonstrate at September Connectathon in Baltimore
  • FITS will be implementing support later this year
  • Project Phase 2: Special Conditions
  • Starting discussions now
slide-12
SLIDE 12

Error Code Set Review:

Review of Guidance

Tracy Little

slide-13
SLIDE 13

Error Code Guidance

Developed following publication of the HL7 2.5.1 rel. 1.5 IG The ERR segment is used to exchange error related data:

  • ERR-2 (Error Location) location of the error in the incoming

message.

  • ERR-3 (HL7 Error Code) indicates the nature of the HL7

(communication) error.

  • ERR-4 (Severity) indicates if the error code being returned is

informational, a warning or an error.

  • ERR-5 (Application Error Code) indicates the nature of the

error that occurred.

  • ERR-8 (User Message) transmits a text to further explain

the nature of the error. Companion spreadsheet: Compiled Error Codes

slide-14
SLIDE 14

Compiled Error Codes Spreadsheet

  • Tracks expanded details for two error code

sets: HL70357 and HL70533

  • HL70357 is the HL7 Error Codes table for

format or technical type errors. This table is “HL7 Defined” and cannot be amended or expanded.

  • HL70533 is the Application Error Codes table

for clinical or administrative type errors related to data reported. This table is a “User Defined” HL7 table and can be expanded.

Where to find this guidance:

  • Natio

ional S Set of

  • f Err

Error Cod Codes

  • Compile

mpiled E Error Codes

Repository keywords: error codes

slide-15
SLIDE 15

Application Error Codes

  • Initially 7 codes in the table
  • Expanded to over 60 codes
  • As you think about

updating/expanding your system’s use of application error codes, start here. Leverage what has already been added if it meets your needs.

Codes are categorized by class

  • Existing (error codes documented in

Release 1.5)

  • Conflicting Data (data within a single

message is internally inconsistent)

  • Inappropriate Date
  • Invalid Data
  • Lookup (an expected record cannot be

found based on data in the message)

  • Message Construction (structural issues

based on local business rules)

  • Missing Data
  • Processing Error
  • Data Sharing
slide-16
SLIDE 16

Further guidance to support sending errors, generating ERR segments

Guida idance ce f for

  • r HL7

HL7 A ACK CK Messages to Support I Interoperabilit ility

Repository keyword: ACK

slide-17
SLIDE 17

Error Code Set Review:

Implementation Demonstration

Kevin Snow

slide-18
SLIDE 18

HL7 Data Quality

Harmonizing HL7 Validation with the AIRA Data Validation Guide and National Error Code Set Guidance

Jan 2019 Feb 2020

slide-19
SLIDE 19

Completeness Consistency Accuracy Timeliness Validity

slide-20
SLIDE 20

The 5Ws (and H)

Who

  • The IIS

What

  • Implement or harmonize with existing data accuracy checks and error codes

Where • HL7 Response Messages When • In real time Why

  • Quick to find, quick to fix. Easier when in harmony with existing resources.

How

  • …and request for feedback!
slide-21
SLIDE 21

Resources Used

https://immregistries.org/resource/

slide-22
SLIDE 22

High Priority accuracy validation

BR-101: Vaccination Encounter Date must not be before Patient Date of Birth

HL7 Data Quality Statement AIRA-DV-BR-101: RXA-3 (DateTimeStartOfAdministration) must not be before PID-7 (DateTimeOfBirth) when RXA-21 (ActionCode) is not valued "D“. When the above data quality statement is violated then return ERR-3 (HL7ErrorCode) 2204^Vaccination Date Too Long Ago^HL70533

slide-23
SLIDE 23

Example

Submit a vaccine the day before the DOB MSH|^~\&|TestApplication|KS9999|WebIZ|KS0000|20060201000000||VXU^V04^VXU_V04|KS99 9938854000000232|T|2.5.1|||ER|AL|||||Z22^CDCPHINVS PID|1||000000002^^^KS9999^MR||SIMPSON^BART^M^^^^L||19990101|M ORC|RE||9999^KS0000 RXA|0|1|19981231||45^hep B, unspec^CVX|999|||01^historical^NIP001||^^^KS9999|||||||||CP|A Should yield ERR||RXA^1^3^1^1|999^ApplicationError^HL70357|E|2204^Vaccination Date Too Long Ago^HL70533^AIRA-DV-BR-101^Vaccination Encounter Date must not be before Patient Date of Birth^L||NumericPath: RXA[1].3[1].1, NamePath: ORDER[0]/RXA/DateTimeStartOfAdministration/Time, RuleId: 148, ApplicationErrorCode: AIRA-DV- BR-101, AIRA Data Validation Guide Rule: BR 101|RXA-3 (DateTimeStartOfAdministration): must not be before PID-7 (DateTimeOfBirth) when RXA-21 (ActionCode) is not valued "D". Please see BR-101 in the AIRA Data Validation Guide.

slide-24
SLIDE 24

High Priority accuracy validation

BR-103: Vaccination Encounter Date must be less than or equal to (before or the same as) the Submission Date

HL7 Data Quality Statement AIRA-DV-BR-103: RXA-3 (DateTimeStartOfAdministration) must be less than or equal to (before or the same as) MSH-7 (DateTimeOfMessage) when RXA-21 (ActionCode) is not valued "D". When the above data quality statement is violated then return ERR-3 (HL7ErrorCode) 1^Illogical Date error^HL70533

slide-25
SLIDE 25

Example

Submit the following MSH|^~\&|TestApplication|KS9999|WebIZ|KS0000|20060201000000||VXU^V04^VXU _V04|KS999938854000000232|T|2.5.1|||ER|AL|||||Z22^CDCPHINVS PID|1||000000002^^^KS9999^MR||SIMPSON^BART^M^^^^L||19990101|M ORC|RE||9999^KS0000 RXA|0|1|20291231||45^hep B, unspec^CVX|999|||01^historical^NIP001||^^^KS9999|||||||||CP|A And you should see the following somewhere in the response ERR||RXA^1^3^1^1|999^ApplicationError^HL70357|E|1^Illogical Date error^HL70533^AIRA-DV-BR-103^Vaccination Encounter Date must be less than or equal to (before or the same as) the Submission Date^L||NumericPath: RXA[1].3[1].1, NamePath: ORDER[0]/RXA/DateTimeStartOfAdministration/Time, RuleId: 73, ApplicationErrorCode: AIRA-DV-BR-103, AIRA Data Validation Guide Rule: BR 103|RXA- 3 (DateTimeStartOfAdministration): must be less than or equal to (before or the same as) MSH-7 (DateTimeOfMessage) when RXA-21 (ActionCode) is not valued "D". Please see BR-103 in the AIRA Data Validation Guide.

slide-26
SLIDE 26

High Priority accuracy validation

BR-107: Every administered vaccine should be recorded as a single Vaccination Event (e.g., combo vaccine should be recorded as 1 event rather than separate events for each component)

Not Implemented Was unsure how to implement due to:

  • Immunizations can be split into multiple messages
  • Even if it’s in a single message the components could be out of order
slide-27
SLIDE 27

High Priority accuracy validation

BR-114: Vaccination Encounter Date should not be the same as the Patient Date of Birth unless it is on the list of vaccines recommended for administration on the date of birth, e.g., HepB

HL7 Data Quality Statement AIRA-DV-BR-114: RXA-3 (DateTimeStartOfAdministration) should not be the same as PID-7 (DateTimeOfBirth) unless it is on the list of vaccines recommended for administration on the date of birth, e.g., HepB when RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D“. When the above data quality statement is violated then return ERR-3 (HL7ErrorCode) 1^Illogical Date error^HL70533

slide-28
SLIDE 28

Example

Case 1) A historic MMR given on the DOB should yield a Warning Step 1) Submit the following message MSH|^~\&|TestApplication|KS9999|WebIZ|KS0000|20060201000000||VXU^V04^VXU_V04|KS999938854000000232|T|2.5.1|||ER |AL|||||Z22^CDCPHINVS PID|1||000000002^^^KS9999^MR||SIMPSON^BART^M^^^^L||19990101|M ORC|RE||9999^KS0000 RXA|0|1|19990101||03^MMR^CVX|999|||01^historical^NIP001||^^^KS9999|||||||||CP|A Step 2) Verify in the response message the presence of the following WARNING ERR||RXA^1^3^1^1|999^ApplicationError^HL70357|W|1^Illogical Date error^HL70533^AIRA-DV-BR-114^Vaccination Encounter Date should not be the same as the Patient Date of Birth for this Vaccine^L||NumericPath: RXA[1].3[1].1, NamePath: ORDER[0]/RXA/DateTimeStartOfAdministration/Time, RuleId: , ApplicationErrorCode: AIRA-DV-BR-114, AIRA Data Validation Guide Rule: BR 114|RXA-3 (DateTimeStartOfAdministration): should not be the same as PID-7 (DateTimeOfBirth) unless it is on the list of vaccines recommended for administration on the date of birth, e.g., HepB when RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D". Please see BR-114 in the AIRA Data Validation Guide.

slide-29
SLIDE 29

High Priority accuracy validation

BR-116: Manufacturer and CVX Code should not contradict one another

Not Implemented Was unsure how to implement due to:

  • How to address case of manufacturer buys out another manufacturer. Does

the code change? Do we need history of this to allow multiple values? Is there a challenge with keeping this up to date?

Functional Guide Vol 2-Review Draft 1.7.19.docx

slide-30
SLIDE 30

High Priority accuracy validation

BR-118: Vaccination Encounter Date should not be after the lot number expiration date

HL7 Data Quality Statement AIRA-DV-BR-118: RXA-3 (DateTimeStartOfAdministration) should not be after RXA-16 (SubstanceExpirationDate) when RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D". When the above data quality statement is violated then return ERR-3 (HL7ErrorCode) 2001^Conflicting Administration Date and Expiration Date^HL70533

slide-31
SLIDE 31

Example

Submit the following message MSH|^~\&|TestApplication|KS9999|WebIZ|KS0000|20060201000000+0000||VXU^V04^VXU_V04|KS999938854000000232|T|2.5.1| ||ER|AL|||||Z22^CDCPHINVS PID|1||000000002^^^KS9999^MR||SIMPSON^BART^M^^^^L||19990101|M ORC|RE||9999^KS0000 RXA|0|1|19990101||08^Hep B, ped/adol^CVX|0.5|mL^^UCUM||00^New admin^NIP001|^Sticker^Nurse^^^^^^^^^^^^^^^^^^RN|^^^KS9999||||lotnum|19981231|SKB^GlaxoSmithKline^MVX|||CP|A RXR|C28161^Intramuscular^NCIT^IM^Intramuscular^HL70162|RT^Right Thigh^HL70163 OBX|1|CE|64994-7^Eligibility Status^LN|1|V02^Medicaid^HL70064||||||F|||19990101|||VXC40^vaccine level^CDCPHINVS OBX|2|CE|30963-3^Vaccine funding source^LN|2|VXC51^Public VFC^NIP008||||||F|||19990101 OBX|3|CE|30956-7^vaccine type^LN|3|45^Hep B, UF^CVX||||||F|||19990101 OBX|4|TS|29768-9^VIS Publication Date^LN|3|19970101||||||F|||19990101 OBX|5|TS|29769-7^VIS Presentation Date^LN|3|19990101||||||F|||19990101 And you should see the following warning in the response ERR||RXA^1^3^1^1|999^ApplicationError^HL70357|W|2001^Conflicting Administration Date and Expiration Date^HL70533^AIRA-DV- BR-118^Vaccination Encounter Date should not be after the lot number expiration date^L||NumericPath: RXA[1].3[1].1, NamePath: ORDER[0]/RXA/DateTimeStartOfAdministration/Time, RuleId: 147, ApplicationErrorCode: AIRA-DV-BR-118, AIRA Data Validation Guide Rule: BR 118|RXA-3 (DateTimeStartOfAdministration): should not be after the lot number expiration date

slide-32
SLIDE 32

Medium Priority accuracy validation

BR-119: Route and Site should not contradict each

  • ther for a given Vaccine Type and Patient’s age

HL7 Data Quality Statement AIRA-DV-BR-119: RXR-1 (Route) and RXR-2 (AdministrationSite) contradict each other for the given Vaccine Type in RXA-5 (AdministeredCode) and Patient’s age on RXA-3 (DateTimeStartOfAdministration) when RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D". When the above data quality statement is violated then return ERR-3 (HL7ErrorCode) 3^Illogical Value error^HL70533

slide-33
SLIDE 33

Example

MSH|^~\&|TestApplication|KS9999|WebIZ|KS0000|20060201000000+0000||VXU^V04^VXU_V04|KS999938854000000232|T|2.5.1| ||ER|AL|||||Z22^CDCPHINVS PID|1||000000002^^^KS9999^MR||SIMPSON^BART^M^^^^L||19990101|M ORC|RE||9999^KS0000 RXA|0|1|19990101||08^Hep B, ped/adol^CVX|0.5|mL^^UCUM||00^New admin^NIP001|^Sticker^Nurse^^^^^^^^^^^^^^^^^^RN|^^^KS9999||||lotnum|20000101|SKB^GlaxoSmithKline^MVX|||CP|A RXR|C28161^Intramuscular^NCIT^IM^Intramuscular^HL70162|LLFA^Left Lower Forearm^HL70163 OBX|1|CE|64994-7^Eligibility Status^LN|1|V02^Medicaid^HL70064||||||F|||19990101|||VXC40^vaccine level^CDCPHINVS OBX|2|CE|30963-3^Vaccine funding source^LN|2|VXC51^Public VFC^NIP008||||||F|||19990101 OBX|3|CE|30956-7^vaccine type^LN|3|45^Hep B, UF^CVX||||||F|||19990101 OBX|4|TS|29768-9^VIS Publication Date^LN|3|19970101||||||F|||19990101 OBX|5|TS|29769-7^VIS Presentation Date^LN|3|19990101||||||F|||19990101 Should yield ERR||RXR^1|999^ApplicationError^HL70357|W|3^Illogical Value error^HL70533^AIRA-DV-BR-119^Route and Site contradiction^L||NumericPath: RXR[1], NamePath: ORDER[0]/RXR, RuleId: , ApplicationErrorCode: AIRA-DV-BR-119, AIRA Data Validation Guide Rule: BR 119|RXR-1 (Route) and RXR-2 (AdministrationSite) contradict each other for the given Vaccine Type in RXA-5 (AdministeredCode) and Patient’s age on RXA-3 (DateTimeStartOfAdministration) when RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D". Please see BR-119 in the AIRA Data Validation Guide.

slide-34
SLIDE 34

High Priority accuracy validation

BR-121: Administered vaccinations coded with an “unspecified” CVX code (should have specific Vaccine Types, e.g., Hib PRP-OMP; unspecified vaccine types, e.g., Hib, unspecified formulation)

HL7 Data Quality Statement AIRA-DV-BR-121: RXA-5 (AdministeredCode) should not be valued with an “unspecified” vaccine when the first occurrence of RXA-9.1 is valued "00" and RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D". When the above data quality statement is violated then return ERR-3 (HL7ErrorCode) 3^Illogical Value error^HL70533

slide-35
SLIDE 35

Example

MSH|^~\&|TestApplication|KS9999|WebIZ|KS0000|20060201000000+0000||VXU^V04^VXU_V04|KS999938854000000232|T|2.5.1|||ER|AL|||||Z22^CDCPHINVS PID|1||000000002^^^KS9999^MR~111111111^^^KS9999^SS||SIMPSON^BART^M^^^^L||19990101|M ORC|RE||9999^KS0000 RXA|0|1|19990101||45^Hep B, UF^CVX|0.5|mL^^UCUM||00^New admin^NIP001|^Sticker^Nurse^^^^^^^^^^^^^^^^^^RN|^^^KS9999||||lotnum|20000101|SKB^GlaxoSmithKline^MVX|||CP|A RXR|C28161^Intramuscular^NCIT^IM^Intramuscular^HL70162|RT^Right Thigh^HL70163 OBX|1|CE|64994-7^Eligibility Status^LN|1|V02^Medicaid^HL70064||||||F|||19990101|||VXC40^vaccine level^CDCPHINVS OBX|2|CE|30963-3^Vaccine funding source^LN|2|VXC51^Public VFC^NIP008||||||F|||19990101 OBX|3|CE|30956-7^vaccine type^LN|3|45^Hep B, UF^CVX||||||F|||19990101 OBX|4|TS|29768-9^VIS Publication Date^LN|3|19970101||||||F|||19990101 OBX|5|TS|29769-7^VIS Presentation Date^LN|3|19990101||||||F|||19990101 Should yield ERR||RXA^1^5^1|999^ApplicationError^HL70357|W|3^Illogical Value error^HL70533^AIRA-DV-BR-121^Administered vaccinations coded with an “unspecified” CVX code^L||NumericPath: RXA[1].5[1], NamePath: ORDER[0]/RXA/AdministeredCode, RuleId: 149, ApplicationErrorCode: AIRA-DV-BR-121, AIRA Data Validation Guide Rule: BR 121|RXA-5 (AdministeredCode): should not be valued with an “unspecified” vaccine when the first occurrence of RXA-9.1 is valued "00" and RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D". Please see BR-121 in the AIRA Data Validation Guide.

slide-36
SLIDE 36

High Priority accuracy validation

BR-130: Doses should not be recorded as given before the minimum patient age or after the maximum patient age for that particular vaccine

HL7 Data Quality Statement AIRA-DV-BR-130: Patient's age on RXA-3 (DateTimeStartOfAdministration) should not be before the minimum patient age or after the maximum patient age for the given Vaccine Type in RXA-5 (AdministeredCode) when RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D". When the above data quality statement is violated then return Next slide…

slide-37
SLIDE 37

Example

1) Hep A given at 9 months of age MSH|^~\&|TestApplication|KS9999|WebIZ|KS0000|20060201000000||VXU^V04^VXU_V04|KS99993885400 0000232|T|2.5.1|||ER|AL|||||Z22^CDCPHINVS PID|1||000000002^^^KS9999^MR||SIMPSON^BART^M^^^^L||19990101|M|||1011 Winward^^Manhattan^KS^66502^^M||^PRN^^^^864^1309701| ORC|RE||9999^KS0000 RXA|0|1|19990901||85^Hep A, UF^CVX|999|||01^historical^NIP001||^^^KS9999|||||||||CP|A Should yield ERR||RXA^1^3^1^1|999^ApplicationError^HL70357|W|3^Illogical Value error^HL70533^AIRA-DV-BR- 130^Vaccine dose given before the minimum patient age or after the maximum patient age^L||NumericPath: RXA[1].3[1].1, NamePath: ORDER[0]/RXA/DateTimeStartOfAdministration/Time, RuleId: , ApplicationErrorCode: AIRA-DV-BR-130, AIRA Data Validation Guide Rule: BR 130, Minimum Date: 19991229, Administration Date: 19990901, Days Difference: 119|Doses should not be recorded as given before the minimum patient age or after the maximum patient age for that particular vaccine

slide-38
SLIDE 38

BR-130 cont.

ERR-3 (HL7ErrorCode) 3^Illogical Value error^HL70533 ERR-7 (DiagnosticInfor mation) NumericPath: RXA[1].3[1].1, NamePath: ORDER[0]/RXA/DateTimeStartOfAdministration/Time, RuleId: , ApplicationErrorCode: AIRA-DV-BR-130, AIRA Data Validation Guide Rule: BR 130, Maximum Date: 20180101, Administration Date: 20181217, Days Difference: 350 ERR-8 (UserMessage) RXA-3 (DateTimeStartOfAdministration): Patient's age on this date should not be before the minimum patient age or after the maximum patient age for the given Vaccine Type in RXA-5 (AdministeredCode) when RXA-20 (CompletionStatus) is valued "CP" or "PA" and RXA-21 (ActionCode) is not valued "D". Please see BR-130 in the AIRA Data Validation Guide. When the above data quality statement is violated then return

slide-39
SLIDE 39

Test and Document Like Crazy

slide-40
SLIDE 40
slide-41
SLIDE 41

Error Code Set Review:

M&I Testing for Error Handling

Nathan Bunker

slide-42
SLIDE 42

Incoming/Ongoing Data Quality

New Content Area Nathan Bunker

42

slide-43
SLIDE 43

Content Area

Transport Submission / Acknowledgment Query / Response CDS Data Quality - Incoming/ongoing

Testing & Discovery Assessment Validation Testing & Discovery Assessment Validation Testing & Discovery Assessment Validation Testing & Discovery Assessment Testing & Discovery

1 2 3

Assessment

43

slide-44
SLIDE 44

Incoming/Ongoing Data Quality

In Incoming/Ongoing Data we are ensuring that IIS can detect if trading partners (e.g., EHRs, pharmacies, etc.) are sending poor data

44

slide-45
SLIDE 45

The Incoming and Ongoing Data Content Area Isn’t Entirely New…

Submission & ACK Incoming & Ongoing Data Quality

Testing and Discovery

Tests what messages the system said they accept/return, and if they’re conformant Tests what the system actually did with the messages…

45

slide-46
SLIDE 46

Incoming/Ongoing Data Quality Scope

  • In Scope
  • The IIS’s ability to detect data quality issues on a per message basis
  • The IIS’s ability to retain and return vaccination events from

submission to query without changing the meaning

  • Out of Scope
  • Data quality monitoring of multiple messages (e.g., percentage of

records submitted with phone number)

  • Patient or vaccine matching/deduplication algorithms
  • Address hygiene/cleansing

46

slide-47
SLIDE 47

Measuring Data Element Data Quality

Step 1

  • Submit

intentionally poor data

  • E.g., Missing,

Invalid, or Conflicting Data Step 2

  • Submit query

for patient Step 3

  • Analyze ACK

and RSP

47

slide-48
SLIDE 48

Example: Invalid DOB

TEST PASS

slide-49
SLIDE 49

Example: Invalid Phone

TEST FAIL OK

slide-50
SLIDE 50

Key Principle

  • For data quality problems the IIS should either:
  • Alert the sending system about the problem, or
  • Not propagate the data quality problem forward
  • IIS should:
  • Have logic in place to detect data quality problems.
  • After detection decide whether to:
  • Send back AE Error, asking submitter to fix and resent
  • Send back AW Warning, asking submitter to fix
  • Be silent on issue, but fix the data before storing
  • Not forward bad data on to other partners
slide-51
SLIDE 51

Data Element Data Quality Issues

  • Missing data: These tests intentionally omit a data element and

submit the record to the IIS.

  • e.g., The IIS detects the first name is empty
  • Invalid data: These tests intentionally submit an illogical value

and submit the record to the IIS.

  • e.g., The IIS detects the phone number has an invalid value of “no phone”
  • Conflicting data: These tests intentionally submit HL7 messages

per the HL7 Implementation guide, but the data within the message is illogical when compared against other data elements

  • e.g., The IIS detects the vaccination date is before the birth date

51

slide-52
SLIDE 52

Patient Demographic Data Elements

  • Patient name: first
  • Patient name: last
  • Patient date of birth
  • Patient gender
  • Patient ID
  • Patient ID type
  • Race
  • Ethnicity
  • Patient multiple birth indicator
  • Patient birth order
  • Patient address: zip code
  • Patient address: state
  • Patient address: country
  • Patient telephone number
  • Patient telephone number type
  • Patient status indicator – provider

level

  • Responsible person name: first
  • Responsible person name: last
  • Responsible person relationship

to patient

52

slide-53
SLIDE 53

Vaccination Event Data Elements

  • Vaccination administration date
  • Vaccine product
  • Vaccine manufacturer
  • Vaccination event record type
  • Vaccine expiration date
  • Vaccine funding source
  • Dose level eligibility
  • Vaccine event ID
  • Contraindications/precautions
  • Contraindication/precaution
  • bservation date
  • Exemptions/refusals
  • Exemption/refusal date

53

slide-54
SLIDE 54

HL7 FAQ

Tracy Little

slide-55
SLIDE 55

What data should be used to populate patient demographics in an RSP response message?

When generating an RSP message, the IIS should echo back the QPD segment received in the QBP query message. This is the patient demographic data sent by the querying system and it should be returned as it was sent. Other segments in the RSP (PID, PD1, NK1) should be populated with data from the responding system’s database. Querying systems may use this data to validate patient selection. Demographic data sent by the querying system in the QPD segment should not be used to populate the PID, PD1 or NK1 segments. The patient ID in QPD-3 should echo what was submitted in the query, but PID-3 can repeat so it can be populated with more than identifier including:

  • The querying system’s MR for the patient.
  • The IIS ID using a value of “SR” in PID-3.5
slide-56
SLIDE 56

Next Meeting

March 12, 2020 2:00 pm ET / 11:00 am PT

slide-57
SLIDE 57

More Information

  • Web Links
  • Subscribe to immunization group

http://www.hl7.org/participate/UserGroups.cfm?UserGroup=Immunization

  • Public User Group Wiki

http://www.hl7.org/special/committees/iug/index.cfm

  • Private User Group Wiki

http://iugwiki.hl7.org/

  • HL7 Press Release

http://www.hl7.org/documentcenter/public_temp_F760602A-1C23-BA17- 0C0D326E635471F9/pressreleases/HL7_PRESS_20140402.pdf

  • AIRA Press Release

http://www.immregistries.org/events/2014/04/10/hl7-immunization-user-group

slide-58
SLIDE 58

Contact Information

If you have any questions or comments:

  • Kim Salisbury-Keith Kim.SalisburyKeith@health.ri.gov
  • Nathan Bunker nbunker@immregistries.org
  • Kevin Snow ksnow@envisiontechnology.com
  • Danny Wise Danny.Wise@allscripts.com

Thank you!