Skip to navigation Skip to content

Medicare eligibility quality checking processing 111-22090030




This document outlines the process for checking a random sample of Medicare eligibility transactions to ensure business rules have been correctly applied. The quality checking process for Medicare eligibility transactions must be conducted in the Consumer Directory Maintenance System (CDMS) environment. Enrolment data is captured from CDMS through the overnight log file of Medicare details for the Quality Control System (QCS).

On this page:

Health Service Delivery Division (HSDD) daily quality checking work items through digitally enabled processing (DEP)

Face to face and non-HSDD staff daily quality checks for Medicare eligibility transactions - get source documents

Face to face and non-HSDD staff daily quality checks for Medicare eligibility transactions - perform check


Health Service Delivery Division (HSDD) daily quality checking work items through digitally enabled processing (DEP)

Table 1: This table outlines how staff in HSDD quality checks the Medicare Eligibility QBBI work items for HSDD staff from PaNDA for post checking.

Expand table

Step

Action

1

Receive new work item

Services Australia uses digitally enabled processing (DEP) to create a PaNDA work item ready for allocation.

To receive a new work item for quality checking in Work Optimiser Worklist, Quality Checker to select the Ready button once.

For more information, see Work Optimiser for staff.

2

Work item details

When selecting a PaNDA work item from Worklist, staff are automatically redirected to the Work Item and Document Details screen.

To open documents associated with the work item:

  • Select the Document ID line to view the document image
  • A new window will open and display the document in a tabular format
  • Information on the right of the table will have the details from Quality Control System (QCS) QBBI needed for checking the work

When staff receive their own work item for checking:

  • add a processing note to the PaNDA record 'own work' and select Save
  • use the HSDD Local Peer Support - SO4's Microsoft team's chat, seek QC support from a Service Officer (SO4) on processing duties to have their work checked
  • SO4 available:
    • Yes - reassign the work item to that staff member using reason code 'Service Support Referral'
    • No - email it to Workload Management Health to reassign the work item. Key 'QBBI QC' in the subject line and the PaNDA work item detail in the body of the email

When staff do not have the skills to check the work item:

  • add a processing note to the PaNDA record 'not trained in worktype' (e.g.: 'not trained in DMX) and select Save
  • click 'unassign' and select reason 'Capability adjusted' in PaNDA. See Table 2 > Step 7 in Work Optimiser for staff
  • add skill and then select relevant details. Check the Capability adjusted Worktype table

3

Access the Quality Control System (QCS)

Log into Medicare Mainframe (CICS) using the Source Office Code (SOC) included in the PaNDA document for completing the quality check.

  • Key 'QBBI,ST/ALL,DOP,OPER/NO' and press [Enter]
    e.g.: QBBI,ST/ALL,DDMMYY,OPER/nnnnn
    Note: key the processing staff logon number without the 'P' letter prefix
  • The QBBI screen displays details of selected transactions
  • Compare the details in the PaNDA document
  • Locate the QBBI line for quality checking. Note: QBBI screen may display with a list of transactions for the OPERNO. Compare and quality check the Medicare card number only listed in the PaNDA document

CDMS transactions selected for quality checking show in the QCS using the legacy (CICS) transaction IDs. The following relationships with the legacy transaction ID and the Medicare eligibility processing activities show:

  • EANU (E2) - register Medicare card details
  • EREU (E1) - amend Medicare card details
  • EFPU (E3) - amend personal details
  • ELNU (E6) - amend Medicare entitlement details
  • ERFU - amend Program Review details

Note: for more information on how to interpret information on the QBBI screen, see the Quality Control System (QCS) for Medicare in Resources.

4

Select transaction to check

To select the transaction to quality check:

  • Place the cursor in the 'S' (select) field
  • Press [Enter]
  • The customer's mainframe enrolment screen shows
  • Press [F3] to return to the QBBI screen

5

Source Documents

Quality checkers must check the transaction against the supporting source documents, which may be located in:

  • PaNDA (Scanned documents)
  • Customer First (Medicare Newborn Manual Enrolment (MAENROL))
  • MEE portal (Digital Medicare Enrolment and Extension)

Note: source documents may not be available for CDMS updates that have resulted from a verbal request.

6

Perform check

Compare the source documents with details in the CDMS history using the CDMS quality control quick reference guide.

If more than one consumer ID needs checking, select the radio button for each individual.

When updates are completed in CDMS as a result from a verbal request, quality check to be completed according to the relevant business rules.

See Resources for link to CDMS reference guide.

7

Record outcome

After examining the transaction and source documents, return to the QCS.

QCS shows b (browse) in the S field and is now ready to accept status codes in the STATUS field to indicate whether the transaction has been processed correctly or incorrectly. See Resources for status codes.

Where no errors are detected, in the STATUS field record the status code as 001.

Where errors are identified in the STATUS fields for the transaction selected, key all status code (critical and non-critical) and press [Enter]. Where more than 4 errors are found, refer to error status E39.

Where a My Health Record error is identified, complete the MHR Registration email template and send to Digital Health Support. See Resources for the template.

QCS returns a lower case u in the S field to advise that the selection has been updated with an error status code.

If several updates have been done in CDMS on the same Medicare card, QCS may select the same card multiple times on the same day. In these cases, quality checkers must only action the first transaction line related to the same Medicare number with a valid status code. Leave additional duplicate transaction lines unactioned. They will automatically be removed from QBBI after 21 days.

8

Provide outcome

Each time a quality check is completed, the quality checker must:

  • email the Service Officer and their Team Leader advising the quality check outcome
  • give feedback with a brief description of the action required by the Service Officer for correction
  • use the relevant QBBI quality checking email template for sending emails. The Resources page contains these templates

Press [F3] to exit the QBBI screen.

9

Complete work item in PaNDA

On completion of quality checking, update the status to Complete on the Work Item and Document Details screen:

  • select Complete in the Status field
  • select Save

A message will display at the bottom of the screen advising that the work item has been successfully saved.

It may take several minutes for the work item to disappear from the Worklist.


Face to face and non-HSDD staff daily quality checks for Medicare eligibility transactions - get source documents

Table 2: This table outlines daily processes for Medicare eligibility quality checking that quality checkers in Face to face and non-HSDD staff must follow.

Expand table

Step

Action

1

Access the Quality Control System (QCS)

Service Officers must log into Medicare Mainframe (CICS).

Key 'QBBI' and press [Enter].

The QBBI screen shows:

  • details of selected transactions from the previous day's processing, and
  • any outstanding transactions not actioned

CDMS transactions selected for quality checking show in the QCS using the legacy (CICS) transaction IDs. The following relationships with the legacy transaction ID and the Medicare eligibility processing activities show:

  • EANU (E2) - register Medicare card details
  • EREU (E1) - amend Medicare card details
  • EFPU (E3) - amend personal details
  • ELNU (E6) - amend Medicare entitlement details
  • ERFU - amend Program Review details

2

Select transaction to check

To select the transaction to quality check:

  • Place the cursor in the 'S' (select) field, and
  • Press [Enter]
  • The customer's mainframe enrolment screen shows
  • Press [F3] to return to the QBBI screen

3

Source Documents

Quality checkers must check the transaction against the supporting source documents, which may be located in:

  • PaNDA (Scanned documents)
  • Customer First (Medicare Newborn Manual Enrolment (MAENROL))
  • Service Officers batch (F2F processing)
  • MEE portal (Digital Medicare Enrolment and Extension)

Note: source documents may not be available for CDMS updates that have resulted from a verbal request.


Face to face and non-HSDD staff daily quality checks for Medicare eligibility transactions - perform check

Table 3: This table outlines daily quality checks for Medicare Eligibility transactions-perform check that quality checkers in Face to face and non-HSDD staff must follow.

Expand table

Step

Action

1

Entitlement Details Inquiry screen
  • Before checking the enrolment, search for all possible customer records:
    • Highlight and copy the Medicare card number from the QCS
    • Go to CDMS and paste the Medicare card number into the Inquire on Consumer Details search screen, then select Entitlement
    • The Entitlement Details Inquiry screen for all members associated with the Medicare card number displays

After checking Medicare details on the Entitlement Details Inquiry screen, do a consumer search to make sure no duplicate records have been created. Complete a Mandatory detailed search in CDMS.

2

Perform check

Compare the source documents with details in the CDMS history using the CDMS quality control quick reference guide.

If more than one consumer ID needs checking, select the radio button for each individual.

When updates are completed in CDMS as a result from a verbal request, quality check to be completed according to the relevant business rules.

See Resources for link to CDMS reference guide.

3

Record check results

After checking the transaction and source documents, return to the QCS.

QCS shows b (browse) in the S field and is now ready to accept status codes in the STATUS field to indicate whether the transaction had been processed correctly or incorrectly. See Resources for status codes.

Where no errors are detected, in the STATUS field record the status code as 001.

Where error are identified, in the STATUS fields for the transaction selected, key all status codes (critical and non-critical) and press [Enter]. Where more than 4 errors are found. refer to error status E39.

Where a My Health Record error is identified complete the MHR Registration email template and send to Digital Health Support if a My Health Record error is identified. See Resources for the template.

QCS returns a lower case u in the S field to advise that the selection has been updated with an error status code.

If several updates have been done in CDMS on the same Medicare card, QCS may select the same card multiple times on the same day. In these cases, quality checkers must only action the first transaction line related to the same Medicare number with a valid status code. Leave additional duplicate transaction lines unactioned. They will automatically be removed from QBBI after 21 days.

4

All transactions checked

After actioning all the appropriate transactions, press [PF3] to exit QCS.

Each time a quality check is completed, the quality checker must:

  • email the Service Officer and their Team Leader advising the quality check outcome
  • give feedback with a brief description of the action required by the Service Officer for correction
  • use the relevant QBBI quality checking email template for sending emails, see Resources for template

5

Paperwork

Manual - (completed by Face to Face Service Officers only)

Endorse the source documents and batch envelope with:

  • QC
  • Quality checker's signature
  • Date

Do not write on the front of source documents. This helps to make sure details do not get covered which allows for reviewing in the future if required.