Table of Contents

Abbreviations 1

Section 1: About the Manual of Procedures 2

A. Purpose of the Manual 2
B. Content Overview 2
C. How to Use the Manual 2

Section 2: ICD-11 Pilot Implementation 3

A. Overview of the Pilot Implementation 3
A.1 Objectives 3
A.2 Scope and Limitations 3
A.3 Roles and Responsibilities of Stakeholders 3
B. Pilot Implementation Framework 4
B.1 Planning Phase 4
B.2 Implementation Phase 5
B.3 Analysis and Report Preparation Phase 5

Section 3: General Guidelines 6

A. ICD-11 API Interoperability 6
B. Morbidity Coding Guidelines 7
B.1 General Coding Guidelines 9
B.2 ICD-10 Specific Coding Guidelines Error! Bookmark not defined.
B.3 ICD-11 Specific Coding Guidelines 9
C. Data Collection 13
C.1 Health Facility 13
C.2 DOH KMITS / DOH-EB 14
D. Monitoring/Assessment 14

Annexes 15
Annex A: Roles and Responsibilities of ICD-11 Stakeholders 15
Annex B: List of Pilot Sites 17
Annex C: Pilot Sites Training Schedule (ICD-11 Training) 19
Annex D: Coding Assessment Tool 21
Annex E: Assignment of ICD-11 Trained Trainer for Coding 22
Assessment/Rating 22
Annex F: Timeline of Pilot Implementation Activities 24
Annex G: Coder- experience survey on the use of ICD-11 coding 26
tool in coding 26
Abbreviations
API Application Programming Interface

CHD Center for Health Development

DOH Department of Health

EB Epidemiology Bureau

HFDB Health Facility Development Bureau

HFDU Health Facility Development Unit

HFSRB Health Facilities and Services Regulatory Bureau

HIMD Health Information Management Department

ICD International Classification of Diseases

IT Information technology

KMITS Knowledge Management and Information Technology Service

MC Main condition

OC Other condition

PHIC Philippine Health Insurance Corporation

PSA Philippine Statistics Authority

PDH Pilot DOH hospital

RESU Regional Epidemiology Surveillance Unit

RLED Regulations, Licensing, and Enforcement Division

1
Section 1: About the Manual of Procedures
A. Purpose of the Manual
This Manual of Procedures (MOP) was developed to provide guidance to the pilot sites -
identified Rural Health Units (RHU) on the pilot implementation for RHUs of the International
Classification of Diseases - 11th Revision (ICD-11) in the Philippines.

Specifically, this MOP intends to:

1. Provide an overview of the pilot implementation, including the specific roles and
responsibilities of concerned stakeholders;
2. Explain the pilot implementation framework; and
3. Outline the coding guidelines on ICD-10 and ICD-11 clinical coding using the iClinicsys
(for RHUs) for the Pilot Implementation

The intended readers of this document are the concerned staff of RHUs identified as pilot
sites, ICD-11 Technical Working Group members, ICD-11 Trained Trainers and Focal persons
from Centers for Health Development (CHDs) and other partner agencies.

B. Content Overview
This document has three (3) major sections:
a. Section 1 (this section) - explains the purpose and the how to use this manual
b. Section 2 - provides an overview of the pilot implementation including the different
phases from planning to analysis and report generation
c. Section 3 - presents the general and specific rules and guidelines on ICD-11 coding
and its IT component

C. How to Use the Manual

This manual is intended for the use of the RHUs identified as pilot sites, ICD-11 TWG
members and ICD Focal Persons from the CHDs for the conduct of the ICD-11 Pilot
implementation. Concerned staff of the identified pilot sites and ICD-11 TWG members shall
use this manual as reference and guide in the conduct of the ICD-11 Pilot Implementation
for hospitals. All concerned are expected to read and understand this manual in order to
standardize the conduct of the ICD-11 Pilot Implementation for RHUs.

2
Section 2: ICD-11 Pilot Implementation
A. Overview of the Pilot Implementation

A.1 Objectives
As part of the Philippines’ transition from ICD-10 to ICD-11, the pilot implementation will be
conducted to identify challenges that need to be addressed for the development of the
policies/guidelines for the complete transition and full implementation.

The specific objectives of the pilot implementation are:

1. To assess and analyze the quality of morbidity coding in ICD-11;
2. To determine possible extension codes in ICD-11 coding needed for the
documented diagnosis;
3. To identify issues in clinical documentation that could affect the quality of coding
with ICD-11;
4. To evaluate the ICD-11 content to cover diagnoses documented in medical records
and identify non-covered terms;
5. To understand coders' and physician’s perspectives on barriers, problems, and
opportunities for ICD-11 implementation; and
6. To identify and document gaps as well as recommendations for the full-blown
implementation of ICD-11 in the country;

A.2 Scope and Limitations

The ICD-11 pilot implementation for hospitals will cover 34 selected RHUs (Annex A). The
selection of the pilot sites was based on the Health Facility readiness assessment results and
the recommendations of KMITS-DOH relative to the iClinicsys use.

The pilot implementation will be from April 1-15, 2023 and will cover ALL cases (morbidity)
from the pilot sites for the period April 1-15, 2023.

A.3 Roles and Responsibilities of Stakeholders

The ICD-11 TWG shall act as the core team responsible for careful planning and execution
of this pilot implementation. Specific roles and responsibilities of stakeholders are provided
in Annex A.

3
B. Pilot Implementation Framework

Preparatory meetings/workshop
Pilot sites identification
Stakeholders Roles and Responsibilities
Development of Pilot Implementation Guidelines
Training
HIM preparation (API interoperability)
Reporting Tool/Mechanism (Data Collection)
Assessment/Monitoring Tool Mechanism
Data perspective (Diagnosis-
Planning related indicators)
User (user experience-related
indicators)
Lessons learned

Pilot sites -dedicated staff

Implementation Support team Coding/IT
(Consulation/Mentoring)
Data Collection/Reporting
Assessment/Monitoring (Meetings)

Analysis Data Analysis

Report Preparation
and Report Dissemination / data utilization
Preparation

Figure 1. Pilot Implementation Framework

B.1 Planning Phase

1. Preparatory meetings/workshop
2. Pilot sites identification
3. Stakeholders Roles and Responsibilities identification
4. Training of Pilot Sites
5. iClinicSys pilot implementation version installation
6. Development of Pilot Implementation Guidelines (MOP) for RHUs
7. Reporting Tool/Mechanism (Data Collection)

4
 8. Assessment/Monitoring Tool Mechanism
•Data perspective (Diagnosis-related indicators)
•Coder (user experience-related indicators)
•Lessons learned

B.2 Implementation Phase

1. Pilot sites ICD-11 trained staff
2. Support team Coding/IT (Consultation/Mentoring)
3. Data Collection
4. Assessment/Monitoring (Meetings)

B.3 Analysis and Report Preparation Phase

1. Data Analysis
2. Report Preparation
3. Dissemination / data utilization

5
Section 3: General Guidelines
A. ICD-11 API Interoperability
● ICD-11 integration in information systems shall follow the WHO guidelines
(https://icd.who.int/en).

● For the purpose of the pilot implementation, ICD-11 is embedded in iClinicSys, one
of the major information systems developed by the DOH that is being implemented
in selected Rural Health Unit (RHU) 00000000000 Health Units.

● Updated diagnosis screen for parallel or dual coding of ICD-10 and ICD-11 (One
field for ICD-10 and another field for ICD-11)

Figure 2. Updated Doctor’s Order on the iClinicSys

● The data entry form in the ICD-11 based EMR system includes:
a. a command field which activates the smart search with the ICD-11
coding tool;
b. one data field which records the ICD-11 code(s) and another data field
which documents the the ICD-11 code title as rendered and selected by
the user in the ICD-11 coding tool;
c. a mechanism which stores the respective ICD-11 URI of the selected
ICD11 entity in the backend.

● In the iClinicSys, the ICD-11 related data fields (e.g. data entry fields to indicate
Main and Other Conditions) shall be linked to the ICD-11 embedded coding tool.

6
 ● Methods of implementation:

TYPE OF FACILITY INFORMATIO METHOD

N SYSTEM
TO BE USED

Rural Health Units with iClinicSys Offline/Web-based version

iClinicSys iClinicSys of iClinicSys

● IT requirements needed in preparation for the iClinicSys pilot implementation

version installation:

1. The Desktop where the iClinicSys will be installed / accessed.

2. The Desktop must have at least of the following:

- Memory: at least 4GB

- Processor: at least 2.20GHz
- Internet Speed: At least 5 Mbps Internet Connection
- OS: Windows 8 or Higher

B. Morbidity Coding Guidelines

Generally, the coding guidelines provided in the ICD-11 Reference Guide shall be followed for
ICD-11 coding.

Table 1. ICD-11 General Features

ICD-11 Features

Coding tool Fully digital with ICD-11 API for easy interoperability

Chapter 26 Chapters and 2 supplementary Sections (Functioning and

Extension Codes)

Arabic

7
 ICD-11 Features

Code Structure ● Alphanumeric

● 4-character code - core
● First character of the code can be a number (1-9) or a
letter (A-S,V and X)
● Remaining characters of the code can be letters or
numbers

Definition of Main Reason for admission, established at the end of the episode of
Condition care.

Use of multiple codes Cluster coding using post coordination

Slash (/) or ampersand (&) used as connector/separator of

codes within a cluster and comma (,) for several clusters

Stem code - can be the only code and/or can be clustered as

the main code with another stem code or an extension code

Extension code - cannot be used alone for disease coding

and cannot be the primary code in a code cluster

“and” as used in category means “and” only

title

Residual category Residual category identified by alphabetic character “Y” and

unspecified category identified by alphabetic character “Z”.

8
B.1 General Coding Guidelines
1. The main condition and other condition(s) relevant to an episode of health care should
have been identified and recorded by the responsible health care practitioner.
2. Review/analyze the documented diagnosis for coding.
3. Code as precise as possible based on available documentation and information.
4. Follow applicable coding conventions and notes.
5. For potentially erroneous documentation, coder must first seek clarification from the
Attending Physician and/or check additional information/documentation available. If these
will not be possible, review record if any indication helps to identify the diagnosed
condition and if record does not help, appropriate Morbidity Modification Rule must be
applied to select/reselect the main condition to be assigned as the primary code, and
6. Always start coding with the ICD-11 coding tool.
7. For injury cases, both the injury and external cause must be recorded and coded with
the nature of injury as the main condition.
8. For delivery cases, outcome of delivery must be coded in addition to the codes for the
details on delivery (indication/complication,method) on the mother’s record.
9. Outcome of delivery code as to place should only be used in coding the baby’s record.
10. For health care related cases, the following three-part quality and safety codes must be
used:

a. Resultant injury or harm.

Code selected from any chapters in ICD–11 except
External Causes chapter.
b. Cause or ‘Mode’ of harm: Code selected from the relevant block in External
Causes chapter
c. ‘Mode/Mechanism’ of harm: Code selected from the relevant block in External
Causes chapter

Note: The three-part model for quality and safety would NOT apply if there is NO
explicit documentation asserting a causal link to another aspect of care,
whether it is a drug, procedure, device or other aspect of care. In such cases,
the medical condition should be coded and postcoordinated with an extension
code for diagnosis timing (ie. XY7V-Postoperative or XY69-Developed after
admission)

B.2 ICD-11 Specific Coding Guidelines

1. Refer to the ICD-11 Reference Guide.
2. If documented, always code the etiology as part of the mandatory code cluster.
3. In principle, codes of all chapters can be combined, except Chapter 26 on Traditional
Medicine and Section V on Functioning.
4. Apply postcoordination (stem and/or extension codes) if applicable (needed information
are available) and appropriate (not yet precoordinated or postcoordinated). Do not
postcoordinate already precoordinated or postcoordinated entities. Category title may also
be considered in determining whether postcoordination would still be applied. Do not apply
postcoordination if the entity title already covers the detail/ information to be
postcoordinated.

9
 a. Only stem codes can be used alone
b. Extension codes are never used alone for disease coding
c. Use “/” as connector of a stem code and another stem code

Example 1: Diabetes type 2 with Diabetic nephropathy

Code cluster: 5A11/GB61.Z

5A11 for Type 2 DM
GB61.Z for Diabetic Nephropathy

d. Use “&” as connector of a stem code to an extension code

Example 1: Leiomyoma of esophagus

Code cluster: 2E86.1&XA0828

2E86.1 for Leiomyoma of other or unspecified sites
XA0828 for site, esophagus

e. Use “,” as connector of several independent cluster of codes

Example: Acute coronary syndrome and hypertensive crisis

Code cluster: BA4Z,BA03

BA4Z for acute coronary syndrome
BA03 for hypertensive crisis

5. Extension Codes

For entities with no suggested postcoordination (mandatory or not), but with additional
details that need to be postcoordinated, postcoordination can be done manually. Stem
and extension codes may be manually postcoordinated as appropriate. For extension
codes, the following extension codes provided in Table 2 below may be used. (Example
for Dehydration, Pneumonia, COVID 19, Tetanus, etc).

Table 2. Extension Codes

Aspect Extension Code

· XK9J Bilateral
1. Laterality · XK8G Left
· XK9K Right
· XK70 Unilateral, unspecified
*No extension code for unspecified
laterality

10
 Aspect Extension Code

2. Risk/Severity level · XS5W Mild

· XS0T Moderate
· XS25 Severe
· XS2R Profound

3. Clinical Staging · XS7A Stage 1

· XS5S Stage 2
· XS4D Stage 2a
· XS6D Stage 2b
· XS00 Stage 3
· XS3T Stage 3a
· XS90 Stage 3b
· XS6G Stage 4
· XS9N Stage 5
· XS88 Stage 6
· XS52 Stage 7
· XS0G Stage 8
· XS2C Stage 9
· XS2X Stage 10

6. Age Group Definitions

For ICD-11 coding purposes, the age groupings in Table 3 shall be considered.

Table 3. Age Groups

Group Age Range

Early Neonatal from birth through the seventh day of life

Late Neonatal from the eighth through the 28th day of life

Middle Childhood from the start of the 5th year of life through
the end of the 10th

Early Adolescence from the start of the 11th year of life through
the end of the 14th

Middle Adolescence from the start of the 15th year of life through
the end of the 17th

Late Adolescence from the start of the 18th year of life through
the end of the 19th

11
 Group Age Range

Young Adult from the start of the 20th year of life through
the end of the 24th

Adult from the start of the 25th year of life through

the end of the 64th

Early Geriatric from the start of the 65th year of life through
the end of the 84th year

Late Geriatric from the start of the 85th year through the
end of life

7. Relational terms and their implication in the arrangement of code/s

Review record if any indication helps to identify the main condition, if none then the
following guidelines shall be followed:

a. “Due to” and other synonymous terms indicating causal relationship

If there is a precoordinated code combining the conditions before and after the
term “due to” then the precoordinated code will be considered for the main
condition code, otherwise, the condition before the term “due to” will be the main
condition.

Example 1 : Diabetic retinopathy due to Type 2 DM

Code cluster: 9B71.0Z/5A11

9B71.0Z for Diabetic Retinopathy (Main condition)

5A11 for Type 2 DM

* except for Sepsis which cannot be considered as main condition if the causing
condition is documented
* a symptom due to a condition must follow the Morbidity Coding Rules MB2 or
MB3 on symptoms for the selection of the main condition

b. “With”, “associated with” and other synonymous terms indicating association, but
not causal relationship

12
 If there is a precoordinated code combining the conditions before and after the
term “with” then the precoordinated code will be considered for the main condition
code, otherwise, the condition before the term “with” will be the main condition.

Example 1 : Diabetes type 2 with Diabetic nephropathy

Code cluster: 5A11/GB61.Z

5A11 for Type 2 DM (Main condition)

GB61.Z for Diabetic Nephropathy

Example 2 : Diabetic retinopathy with Type 2 DM

Code cluster: 9B71.0Z/5A11

9B71.0Z for Diabetic Retinopathy (Main condition)

5A11 for Type 2 DM

* a symptom associated with a diagnosed condition must follow the Morbidity

Coding Rule MB2 on symptoms for the selection of the main condition

C. Data Collection
C.1 Health Facility

To code the diagnosis using the ICD 11 tools, access the Doctor's Order module
in the patient’s consultation in iClinicSys.

Figure 3. iClinicSys Process Flow - Consultation Module

13
C.2 DOH KMITS / DOH-EB
Coded data from the iClinicsys will be extracted weekly (Annex F) for assessment using the
Assessment tool in Annex D. Identified ICD-11 trained trainers will be assigned for the coding
assessment/rating (Annex E).

A tool will be provided in n iClinicSys for the facility to use in extracting the data needed to
be sent to EB focal persons who will transfer the coded data to the assessment tool template.

D. Monitoring/Assessment
Extracted coded data will be transferred to the assessment tool template per facility and will
be shared to the assigned ICD-11 trained trainers via google sheet for their coding
assessment/rating. A viber group of assigned ICD-11 trained trainers will be created to
facilitate coordination and discussion of ratings.

Online meetings will be scheduled to discuss and analyze the coding ratings. Significant
difference in the proportion of correct and incorrect coding will be determined using
appropriate statistical tools.

For the assessment of the coder as user of the ICD-11 coding tool, a brief survey will be
administered at the end of the 3-week coding using the Coder-Experience Survey Form
(Annex G) which will be administered through the google form and analyze using appropriate
statistical tools.

14
Annexes

Annex A: Roles and Responsibilities of ICD-11 Stakeholders

Different stakeholders are crucial in the success of this pilot implementation. The specific
roles and responsibilities per stakeholder are outlined in the table below.

STAKEHOLDER ROLES AND RESPONSIBILITIES

DOH-EB 1. Lead in the coordination for engagement with identified

stakeholders.
2. Coordinate, organize and conduct ICD-11 training of
concerned staff of the identified pilot sites (hospitals).
3. Trained trainers to be part of the training team for the
training of concerned staff of the identified pilot sites.
4. Oversee the conduct of the ICD-11 pilot implementation
i. Data collection
ii. Data recording
iii. Data analysis
5. Provide technical support (onsite or virtual) on coding
to pilot sites during implementation.

DOH-KMITS 1. Ensure the proper installation of ICD-11 API to the HIS

that will be used for the pilot implementation Rural
Health Units (iClinicSys).
2. Develop guidelines on the integration of the EMR
(iClinicSys) with the ICD-11 API and embedded ICD-11
coding tool.
3. Provide support (onsite or virtual) to pilot sites on
installation and troubleshooting relative to the ICD-11
API interoperability with the EMR (iClinicSys) before and
during the implementation

DOH-HFSRB 1. Provide support relative to coordination with identified

Health Facilities included as pilot sites.

CHDs/MOHs (RESU, 1. CHD/MOH ICD Focal Persons trained as trainers to be

HFDU, RLED, IT) part of the training team for the training of concerned
staff of the identified pilot sites.
2. Provide technical support (onsite or virtual) on coding
and API related concerns to pilot sites during
implementation.

15
PHIC 1. Trained Trainers to provide technical support (onsite or
virtual) on coding and API related concerns to pilot
sites during implementation.

PSA 1. Trained trainers to provide technical support (onsite or

virtual) on coding and API related concerns to pilot
sites during implementation.

ICD-11 Trained 1. To provide technical support (onsite or virtual) on

Trainers coding and API related concerns to pilot sites during
implementation.

Identified Rural Health 1. To commit to participate in the ICD-11 Pilot

Units (pilot sites) Implementation including related activities such as but
not limited to training.
2. To nominate 2 dedicated/qualified staff involved in the
iClinicsys implementation in the RHU to be trained on
ICD-11 who will form part of the team in the health
facility for the ICD-11 pilot implementation
a. Physician
b. Non Medical staff
3. To ensure the functionality and reliability of the
institutional IT system for ICD-11 pilot
testing/implementation
4. To participate in the ICD-11 pilot implementation and
follow set guidelines

16
Annex B: List of Pilot Sites

REGION RHUs

1 NCR Mandaluyong City Health Office

2 Parañaque City Health Office

3 Valenzuela City Health Office

4 Quezon City Health Office

5 CAR Atab District Health Center

6 Tayum Rural Health Unit

7 REGION I Bayambang Rural Health Unit

8 Santol Rural Health Unit

9 REGION II Santiago City Isabela Health Office

10 Tuao I Cagayan Rural Health Unit

11 REGION III Balanga Rural Health Unit II

12 REGION IV A Ibaan Rural Health Unit

13 Rodriguez Rural Health Unit I (CCH Rural Health

Unit Birthing Home- Municipal Health Office)

14 Rosario Rural Health Unit Cavite

17
 REGION RHUs

15 REGION IV B Magsaysay Palawan Rural Health Unit

16 Cuyo Rural Health Unit

17 Calintaan Rural Health Unit

18 REGION V Bulan Rural Health Unit

19 Daet Rural Health Unit I

20 REGION VI Altavas Rural Health Unit

21 REGION VII Bais City Health Office

22 Danao City Health Office

23 REGION VIII Barugo Rural Health Unit

24 REGION IX Buug Rural Health Unit

25 Diplahan Rural Health Unit

26 Tungawan Rural Health Unit

27 REGION X Maramag Municipal Health Office And Birthing Home

28 Pangantucan Rural Health Unit

29 REGION XI District C - Mini Forest Health Center/City Health

Office Davao

18
 REGION RHUs

30 REGION XII Kidapawan City Health Office

31 Polomolok Rural Health Unit

32 REGION XIII Claver Rural Health Unit

33 Lianga Municipal Health Unit

34 BARMM Buluan Rural Health Unit

Annex C: Pilot Sites Training Schedule (ICD-11 Training)

Total No. of 1ST BATCH 2nd BATCH

facilities/ (February 6-10, (February 13-17,
participant 2023) 2023)

Pilot Sites - 34 RHUs 16 RHUs 18 RHUs

identified
RHUs ( 2 staff/RHU who
are involved in
the iClinicsys
implementation in
the RHU:
1- MD;

19
1- Non Medical
staff)

20
 Annex D: Coding Assessment Tool

Rating for ICD-11 Coding*

PATIENT AGE
Facility Date of Patient Patient’s Final Diagnosis ICD-11
Name Encounter/ No. Sex code/s
Admission PATIENT MC code Additiona REMARKS
PATIENT AGE PATIENT PATIENT
AGE (primary l code/s
YEAR AGE DAY AGE HOUR code) (if any)
MONTH

* Coding ratings: 1 - correct code/s

.5 - incomplete code/s - code for the correct condition (MC and other) not complete,
ie. lacking required extension character/postcoordination code/s
0 - incorrect code (including incorrect main/other condition selected and/or
incorrect code for the correct main/other condition)

Remarks - to indicate any comment/s regarding the coding done and whether the final diagnosis provided was complete
(ie. for injury-the nature and circumstance must be indicated, for delivery- the outcome of delivery is provided, etc.)
and other relevant findings noted.

21
Annex E: Assignment of ICD-11 Trained Trainer for Coding
Assessment/Rating

REGIO RHUs Assigned ICD-11 TOT Trained

N for coding assessment/rating
(to be determined)

1 NCR Mandaluyong City Health Office TOT trained in NCR CHD, PSA,
PHIC
2 Parañaque City Health Office

3 Valenzuela City Health Office

4 Quezon City Health Office

5 CAR Atab District Health Center TOT trained in CAR CHD

6 Tayum Rural Health Unit

7 REGION Bayambang Rural Health Unit TOT trained in Ilocos CHD

I

8 Santol Rural Health Unit

9 REGION Santiago City Isabela Health Office TOT trained in Cagayan Valley CHD
II
10 Tuao Rural Health Unit I (West)

11 REGION Balanga Rural Health Unit II TOT trained in Central Luzon CHD
III CHD

12 Ibaan Rural Health Unit

22
 REGIO RHUs Assigned ICD-11 TOT Trained
N for coding assessment/rating
(to be determined)

13 REGION Rodriguez Rural Health Unit I (CCH TOT trained in CALABARZON CHD,
IV A Rural Health Unit Birthing Home- HIM org,
Municipal Health Office)

14 Rosario Rural Health Unit Cavite

15 REGION Magsaysay Palawan Rural Health TOT trained in MIMAROPA CHD, EB

IV B Unit

16 Cuyo Rural Health Unit

17 Calintaan Rural Health Unit

18 REGION Bulan Rural Health Unit TOT trained in Bicol CHD

V
19 Daet Rural Health Unit I

20 REGION Altavas Rural Health Unit TOT trained in Western Visayas

VI CHD

21 REGION Bais City Health Office TOT trained in Central Visayas CHD
VII

22 Danao City Health Office

23 REGION Barugo Rural Health Unit TOT trained in Eastern Visayas

VIII CHD

24 REGION Buug Rural Health Unit TOT trained in Zamboanga

IX Peninsula CHD
25 Diplahan Rural Health Unit

26 Tungawan Rural Health Unit

23
 REGIO RHUs Assigned ICD-11 TOT Trained
N for coding assessment/rating
(to be determined)

27 REGION Maramag Municipal Health Office TOT trained in Northern Mindanao

X And Birthing Home CHD

28 Pangantucan Rural Health Unit

29 REGION District C - Mini Forest Health TOT trained in Davao CHD

XI Center/City Health Office Davao

30 REGION Kidapawan City Health Office TOT trained in SOCCSKSARGEN

XII CHD

31 Polomolok Rural Health Unit

32 REGION Claver Rural Health Unit TOT trained in CARAGA CHD

XIII

33 Lianga Municipal Health Unit

34 BARMM Buluan Rural Health Unit TOT trained in MOH BARMM

24
Annex F: Timeline of Pilot Implementation Activities

Activity Week 1 Week 2 Week 3 Week 4 Week 5

April 1-8, April 9-15, April 16-22, April 23-30, May 1-5,
2023 2023 2023 2023 2023

Pilot Coding of Coding of

implementation data data

Data extraction Extraction of Extraction of

from iClinicsys Week 1 Week 2
coded data coded data
on April 9, on April 23,
2023 2023

Coding Assessment/ Assessment/ Assessment/ Assessment/

assessment/ rating of rating of rating of rating of
rating Week 1 Week 1 Week 2 coded Week 2
coded data coded data data coded data

Coder
experience
survey

Meetings for as needed as needed as needed May 5, 2023

Data
Analysis/Report
Preparation

25
Annex G: Coder- experience survey on the use of ICD-11 coding
tool in coding
1. Name of Facility _______________________________________________________
2. Name of Coder _______________________________________________________
3. Total number of cases coded in ICD-11 _____________________________________

4. In general, was the documented diagnosis for the case coded complete?

___ Yes, in all cases coded

___ Yes, only in about 50% of the cases coded
___ Yes, only in less than 50% of the cases coded

5. Did you find the exact ICD-11 code/s you were looking for in the ICD-11 coding tool (ICD-
11 MMS and Coding Tool)?

___ Yes, in all cases coded

___ Yes, only in about 50% of the cases coded
___ Yes, only in less than 50% of the cases coded

What was lacking in ICD-11 code provided in the ICD-11 coding tool?
__________________________________________________________

6. In general, how easy was it to find the code using the ICD-11 coding tools?

___ Fairly easy

___ Moderate
___ Difficult

What made it difficult to find the code? __________________________

7. In general, the time it took you to find the code using the ICD-11 coding tools was

___ Fairly acceptable

___ Moderate
___ Unacceptably long

What caused the unacceptably long time it took you to find the code?
__________________________________________________________

Do you have additional comments on the following:

a. iClinicSys diagnosis screen

26
 _________________________________________________________________

b. Documentation of the diagnosis and other information

_________________________________________________________________

c. ICD-11 coding tool

_________________________________________________________________

d. ICD-11 content (entities, convention, rules, etc.)

_________________________________________________________________

e. Recommendation for inclusion in the guidelines for the full implementation of ICD-
11
________________________________________________________________

THANK YOU

27