<?xml version="1.0"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "JATS-journalpublishing1.dtd"[]>
<article xml:lang="en" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" dtd-version="1.2" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">IJPDS</journal-id>
<journal-title-group>
<journal-title>International Journal of Population Data Science</journal-title>
<abbrev-journal-title>IJPDS</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">2399-4908</issn>
<publisher>
<publisher-name>Swansea University</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.23889/ijpds.v8i5.2935</article-id>
<article-id pub-id-type="publisher-id">8:5:03</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Population Data Science</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Data Note: Alternative Name Encodings - Using Jyutping or Pinyin as tonal representations of Chinese names for data linkage</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author"><name><surname>Lam</surname><given-names initials="J">Joseph</given-names></name><xref ref-type="aff" rid="affil-1">1</xref><xref ref-type="corresp" rid="correspondingAurthor">*</xref></contrib>
<contrib contrib-type="author"><name><surname>Cortina-Borja</surname><given-names initials="M">Mario</given-names></name><xref ref-type="aff" rid="affil-1">1</xref></contrib>
<contrib contrib-type="author"><name><surname>Aldridge</surname><given-names initials="R">Robert</given-names></name><xref ref-type="aff" rid="affil-2">2</xref></contrib>
<contrib contrib-type="author"><name><surname>Blackburn</surname><given-names initials="R">Ruth</given-names></name><xref ref-type="aff" rid="affil-1">1</xref></contrib>
<contrib contrib-type="author"><name><surname>Harron</surname><given-names initials="K">Katie</given-names></name><xref ref-type="aff" rid="affil-1">1</xref></contrib>
<aff id="affil-1"><label>1</label><institution>Great Ormond Street Institute of Child Health, University College London, London, UK</institution></aff>
<aff id="affil-2"><label>2</label><institution>Institute for Health Metrics and Evaluation, University of Washington, Seattle, USA</institution></aff>
</contrib-group>
<author-notes>
<corresp id="correspondingAurthor"><label>*</label>Corresponding author: Joseph Lam <email>joseph.lam.18@ucl.ac.uk</email></corresp>
<fn fn-type="conflict">
<label>Conflict of interests</label>
<p>All authors declare no competing interests.</p>
</fn>
</author-notes>
<pub-date date-type="pub" publication-format="electronic"><day>11</day><month>03</month><year>2025</year></pub-date>
<pub-date date-type="collection" publication-format="electronic"><year>2023</year></pub-date>
<volume>8</volume>
<issue>5</issue>
<elocation-id>2935</elocation-id>
<permissions>
<license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by-nc-nd/4.0/">
<license-p>This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.</license-p>
</license>
</permissions>
<self-uri xlink:href="https://ijpds.org/article/view/2935">This article is available from the IJPDS website at: https://ijpds.org/article/view/2935</self-uri>
<abstract>
<p>Accurate data linkage across large administrative databases is crucial for addressing complex research and policy questions, yet linkage errors&#x2014;stemming from inconsistent name representations&#x2014;can introduce biases, predominantly for names not given in English. This data note examines the impact of romanisation on linkage accuracy, focusing on Chinese names and comparing standardised systems (Jyutping and Pinyin) with the non-standardised Hong Kong Government Cantonese Romanisation (HKG-romanisation). We identify three primary issues: language-specific variations in romanisation, the loss of tonal information inherent to tonal languages, and discrepancies in name order conventions. Using a dataset of 771 Hong Kong student names, our analysis reveals that standardised romanisation systems enhance the uniqueness and consistency of name representations, thereby improving linkage precision and recall compared to HKG-romanisation. Specifically, Jyutping and Pinyin achieved over 95% recall in blocking strategies, whereas HKG-romanisation only reached 68.8%. Incorporating tonal information further improved recall. These findings underscore the necessity of adopting standardised, tone-sensitive romanisation systems and flexible database designs to reduce linkage errors and promote data equity for under-represented groups. We advocate for the implementation of phonetic encodings in databases, alongside language-specific pre-processing protocols, to ensure more inclusive and accurate data linkage processes.</p>
</abstract>
<kwd-group>
<kwd>data linkage</kwd>
<kwd>romanisation</kwd>
<kwd>linkage errors</kwd>
<kwd>data equity</kwd>
</kwd-group>
</article-meta>
</front>
<body>
<sec>
<title>Context</title>
<sec>
<title>Differential linkage errors through romanisation</title>
<p>Data linkage is used increasingly across large administrative databases to enhance data resources to allow addressing complex research and policy questions [<xref ref-type="bibr" rid="ref-1">1</xref>]. Accurate data linkage is important as linkage errors can undermine the quality of the linked data by introducing selection bias, and limiting researchers&#x2019; ability to accurately represent the targeted populations [<xref ref-type="bibr" rid="ref-2">2</xref>]. In data linkage, names are often used as key identifiers to decide if records from multiple data sources belong to the same person.</p>
<p>Romanisation refers to the transformation of names in local languages to a commonly operable language, which is English in most developed countries in the Global North. Romanisation can be viewed as a process of encoding that selectively retains information operable in (Western) databases (e.g. only containing Latin-based alphabets), and drops information deemed irrelevant or too costly to retain, such as using American Standard Code for Information Interchange (ASCII) for encoding. Unicode is an improvement over ASCII with greater flexibility on type of characters it could encode, but still does not provide tonal representations. Other examples relate to data system designs, people with multiple surnames (e.g. common in Spain and Latin-American countries) might only be allowed to provide one or use hyphenated versions, or letters not in the English alphabet and diacritical marks might be ignored or misrepresented. Romanisation is not always standardised, e.g. there are over 10 different systems for Arabic [<xref ref-type="bibr" rid="ref-3">3</xref>].</p>
<p>When romanised names are not consistently represented in databases, linkage errors are more likely to occur (i.e. false matches, where records belonging to different people are linked together, or missed matches, where records belonging to the same person remain unlinked). As large-scale linked administrative data are used more readily by health professionals and policy makers to generate evidence and drive decisions, this disparity in linkage rates perpetuates health and social inequities for under-represented groups, such as migrants and people from ethnic minoritised communities [<xref ref-type="bibr" rid="ref-4">4</xref>, <xref ref-type="bibr" rid="ref-5">5</xref>]. For example, a historical linkage of census data from the United States matched only 3.6% of male Chinese migrants between 1880-1900 compared to 16.3% of English migrants [<xref ref-type="bibr" rid="ref-6">6</xref>]. A recent linkage of asylum and resettled refugees with census data in the United Kingdom found a substantial difference in linkage rates by language and country of origin [<xref ref-type="bibr" rid="ref-7">7</xref>]. There is a growing proportion of births in England (37%) and London (66%) to families where one or both parents were born outside the UK; between 2013-2017, 53% of singleton child births in New York City were born to non-US-born mothers [<xref ref-type="bibr" rid="ref-8">8</xref>]. Use of poorly romanised and processed names in data systems will selectively and continually under-represent subpopulations in results, if current data linkage &#x2018;blind spots&#x2019; or structural barriers in data systems to inclusion in linked datasets are not actively addressed.</p>
<p>Building on Postel&#x2019;s work on Chinese-specific pre-processing for historical linkage [<xref ref-type="bibr" rid="ref-9">9</xref>], this data note describes three problems faced by, but not unique to representing Chinese characters for data linkage. We compare standardised romanisation of Cantonese (Jyutping) [<xref ref-type="bibr" rid="ref-10">10</xref>], Mandarin (Pinyin) [<xref ref-type="bibr" rid="ref-11">11</xref>], with the non-standardised Hong Kong Government Cantonese Romanisation system (HKG-romanisation) [<xref ref-type="bibr" rid="ref-12">12</xref>], as a case example. We then propose a solution model for alternative name encodings, by demonstrating the advantages of challenging current standard practices in global information systems to improve linkage and promoting data equity [<xref ref-type="bibr" rid="ref-13">13</xref>].</p>
</sec>
</sec>
<sec>
<title>Data issues</title>
<sec>
<title>Three problems with processing Chinese characters and names</title>
<sec>
<title>Language-specific romanisation</title>
<p>Theoretically, Jyutping or Pinyin should more accurately represent pronunciations compared to the HKG-romanisation system. However, not all variations in romanised representations arise from flaws in the romanisation system. Instead, there are historic-, country- and language-specific variations in how some Chinese characters are represented in different geographic regions and countries. This variation is informative for linkage, because it can help distinguish between different people with similar names. <xref ref-type="fig" rid="fig-1">Figure 1</xref> shows the variations in representation of a common surname <inline-graphic xlink:href="ijpds-06-2935-infig01.tif"/> in Cantonese, Mandarin, Vietnamese, Malaysian/Singaporean, Indonesian, Japanese, Korean, and other dialects. <inline-graphic xlink:href="ijpds-06-2935-infig02.tif"/> is most commonly pronounced as &#x201C;Lin&#x201D; by Mandarin speakers. These variations <inline-graphic xlink:href="ijpds-06-2935-infig03.tif"/> of are not a result of inconsistent romanisation, but a reflection of how that character is pronounced locally, and how such pronunciations change over time within the same region. Using a single unified romanisation system for Chinese characters from all countries would mean these language-specific and temporal-specific distinctions are lost. Knowing the country of origin and language system of the individuals may help to identify the best romanisation approach to retain most relevant information.</p>
<fig id="fig-1">
<label>Figure 1</label>
<caption><p>Illustration of different ways the character <inline-graphic xlink:href="ijpds-06-2935-infig04.tif"/> is romanised and pronounced by countries and languages. Photo by Johannes Plenio: <uri>https://www.pexels.com/photo/two-brown-trees-1632790/</uri></p></caption>
<graphic xlink:href="ijpds-06-2935-g001.tif"/>
</fig>
</sec>
<sec>
<title>Non-tonal representation of a tonal language</title>
<p>Modern databases were developed for Indo-European languages in mind using Latin-based alphabets. With rare exceptions such as Panjabi (Punjabi) [<xref ref-type="bibr" rid="ref-14">14</xref>], Indo-European languages do not differentiate tones in how they are spoken. This means that even if local languages were perfectly represented by roman alphabets, romanised names will still be less specific and distinctive than their original names as tonal information is not retained. This loss of granularity degrades the identifying information available and could lead to linkage errors. This is a particular problem for HKG-romanisation and Pinyin, as intonations are not represented in the former, and not properly recorded in the latter as diacritics (notations on top of each word that are necessary for tones) are often ignored. Jyutping and a properly recorded Pinyin system are more sensitive to tonal changes, and a more consistent representation of Chinese characters than HKG-romanisation.</p>
</sec>
<sec>
<title>Name orders</title>
<p>A common issue for character-based languages is the misplacement of character orders. For example, Chinese surname and forename are often inverted due to different naming conventions; forename characters are sometimes misplaced as middle names [<xref ref-type="bibr" rid="ref-15">15</xref>]. The latter is more prevalent in HKG-romanisation and Jyutping, as each character is separated by a space; and less so for Pinyin as there is no space between forename characters. The inability to segment which characters belong to surname or forename fields means that linkages may be inaccurate. Previous attempts, e.g. the Abramitzky, Boustan, Eriksson (ABE) method [<xref ref-type="bibr" rid="ref-6">6</xref>], to pre-process multi-part names have resorted to clustering multi-part names to their first character, e.g. clustering &#x201C;Chin Fung&#x201D;, &#x201C;Chin Hing&#x201D;, &#x201C;Chin Lung&#x201D; as &#x201C;Chin&#x201D;. Note that these are all HKG-romanisation; linking Cantonese-based romanised names would be predominantly impacted using the ABE method. Chinese surnames are already less specific for linkages than English, with larger clusters of people sharing the same common surnames (<xref ref-type="supplementary-material" rid="sup-a">Appendix 1</xref>). The ABE method further lowers the specificity of Chinese forenames, resulting in linkages that are more prone to false matches. Postel demonstrated that proper segmentation, indexing and ordering of Chinese characters could substantially improve linkage rates for Chinese names [<xref ref-type="bibr" rid="ref-9">9</xref>].</p>
<p>In the following section, we will compare the utility of Jyutping, Pinyin and HKG-romanisation in representing Chinese characters, sensitive to language-specific romanisation, tonal representation and name orders.</p>
</sec>
</sec>
<sec>
<title>Proposed solution</title>
<p>We scraped online student class lists from schools in Hong Kong that provided both Chinese and English Names (<italic>n</italic> = 774). We only included names that had a Mandarin or Cantonese origin, based on the provided Chinese and (romanised) English names (<italic>n</italic> = 771). Records providing English names with no space within forename characters, or use of non-accented Pinyin as English names reflect a Mandarin origin.</p>
<p>We derived Jyutping and Pinyin using the pinyin_jyutping package [<xref ref-type="bibr" rid="ref-16">16</xref>] in Python 3.8 [<xref ref-type="bibr" rid="ref-17">17</xref>], which used an online open-source Cantonese dictionary CC-Canto [<xref ref-type="bibr" rid="ref-18">18</xref>], for each character of the Chinese name. Jyutping and Pinyin tones are represented using numbers: 1-6 for Cantonese and 1-5 for Mandarin. We provided a short introduction to Chinese names and romanisation systems in <xref ref-type="supplementary-material" rid="sup-a">Appendix 1</xref>. We manually entered the records that the package failed to translate, and stored pronunciations and tones in separate columns. Raw name list, cleaned data and codes are available from a University College London Research Data Repository [<xref ref-type="bibr" rid="ref-19">19</xref>].</p>
<p>Of the 771 included names, a large majority (97.7%) had a 3-character full name, most (83.9%) had a romanised English forename, and most names were given based on Cantonese (97.4%) (<xref ref-type="table" rid="table-1">Table 1</xref>).</p>
<table-wrap id="table-1">
<label>Table 1</label><caption><title>Descriptive characteristics of Chinese and English names in the study dataset</title></caption>
<table frame="hsides" rules="groups">
<col width="30%"/>
<col width="30%"/>
<col width="20%"/>
<col width="20%"/>
<tbody>
<tr>
<td align="left" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"></td>
<td align="center" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>Descriptive characteristics</bold></td>
<td align="center" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>Count</bold></td>
<td align="center" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>%</bold></td>
</tr>
<tr>
<td align="left" valign="top">Total <italic>n</italic></td>
<td align="center" valign="top"></td>
<td align="center" valign="top">771</td>
<td align="center" valign="top">100</td>
</tr>
<tr>
<td colspan="4" align="left" valign="top">Chinese surname</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="center" valign="top">1 Character</td>
<td align="center" valign="top">771</td>
<td align="center" valign="top">100</td>
</tr>
<tr>
<td colspan="4" align="left" valign="top">Chinese forename</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="center" valign="top">1 Character</td>
<td align="center" valign="top">17</td>
<td align="center" valign="top">2.3</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="center" valign="top">2 Characters</td>
<td align="center" valign="top">754</td>
<td align="center" valign="top">97.7</td>
</tr>
<tr>
<td colspan="4" align="left" valign="top">English forename</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="center" valign="top">Romanised only (e.g. Chin Hang)</td>
<td align="center" valign="top">647</td>
<td align="center" valign="top">83.9</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="center" valign="top">English only (e.g. Johnny)</td>
<td align="center" valign="top">27</td>
<td align="center" valign="top">3.5</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="center" valign="top">Both English and romanised (e.g. Chin Hang Johnny)</td>
<td align="center" valign="top">97</td>
<td align="center" valign="top">12.6</td>
</tr>
<tr>
<td colspan="4" align="left" valign="top">Language</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="center" valign="top">Cantonese</td>
<td align="center" valign="top">751</td>
<td align="center" valign="top">97.4</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="center" valign="top">Mandarin</td>
<td align="center" valign="top">20</td>
<td align="center" valign="top">2.6</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>We compared how closely three different systems of romanisation (HKG-romanisation, Jyutping, Pinyin) represented the original Chinese characters, in terms of uniqueness, which provided some information on the utility of these systems for balancing sensitivity and specificity of linkages.</p>
<p>Our sample of 771 individuals all had unique Chinese full names and shared 123 unique surnames (<xref ref-type="table" rid="table-2">Table 2</xref>). The top five most frequent surnames accounted for over 30% of surnames. HKG-romanisation resulted in 152 unique surnames with 29 extra surnames than Chinese. Both Jyutping and Pinyin reduced the number of unique representations of names. The HKG-romanisation system represented different Chinese characters using the same codes, for example, &#x201C;Chiu&#x201D; is used to represent <inline-graphic xlink:href="ijpds-06-2935-infig05.tif"/> (Jyutping: Ziu6, Pinyin: Zhao4) and <inline-graphic xlink:href="ijpds-06-2935-infig06.tif"/> (Jyutping: Jau1, Pinyin: Qiu1). The HKG-romanisation also represented the same Chinese characters using different codes, for example, <inline-graphic xlink:href="ijpds-06-2935-infig07.tif"/> is represented as &#x201C;Chow&#x201D;, &#x201C;Chau&#x201D;, or &#x201C;Chiau&#x201D;, where Jyutping would consistently represent it as &#x201C;Zau1&#x201D;, and Pinyin &#x201C;Zhou1&#x201D;. Both Jyutping and Pinyin represented the same characters consistently, but both represented different characters using the same codes, for example, &#x201C;Wong4&#x201D; for both <inline-graphic xlink:href="ijpds-06-2935-infig08.tif"/> and in Jyutping, <inline-graphic xlink:href="ijpds-06-2935-infig09.tif"/> and &#x201C;Yan2&#x201D; for both <inline-graphic xlink:href="ijpds-06-2935-infig10.tif"/> and <inline-graphic xlink:href="ijpds-06-2935-infig11.tif"/> in Pinyin. Pinyin without tones had all the problems of Pinyin, plus the inability to differentiate tones, hence was less specific.</p>
<table-wrap id="table-2">
<label>Table 2</label><caption><title>Count of unique values at each field using Chinese characters, Jyutping, Pinyin, Pinyin_notone (without tonal information) and HKG-romanisation for 771 names. In brackets, degree of loss or addition of unique values, using different romanisation methods compared to original Chinese characters (%)</title></caption>
<table frame="hsides" rules="groups">
<col width="25%"/>
<col width="15%"/>
<col width="15%"/>
<col width="15%"/>
<col width="15%"/>
<col width="15%"/>
<tbody>
<tr>
<td align="left" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>Unique count</bold></td>
<td align="center" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>Chinese</bold></td>
<td align="center" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>Jyutping</bold></td>
<td align="center" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>Pinyin</bold></td>
<td align="center" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>Pinyin_notone</bold></td>
<td align="center" style="border-top: solid 1pt; border-bottom: solid 1pt;" valign="middle"><bold>HKG-romanisation</bold></td>
</tr>
<tr>
<td align="left" valign="top">Surname (1 char)</td>
<td align="center" valign="top">123</td>
<td align="center" valign="top">117 (&#x2212;4.9%)</td>
<td align="center" valign="top">120 (&#x2212;2.4%)</td>
<td align="center" valign="top">108 (&#x2212;12.2%)</td>
<td align="center" valign="top">152 (+23.6%)</td>
</tr>
<tr>
<td align="left" valign="top" style="padding-left:1em">1-to-1</td>
<td align="center" valign="top"></td>
<td align="center" valign="top">35</td>
<td align="center" valign="top">39</td>
<td align="center" valign="top">34</td>
<td align="center" valign="top">27</td>
</tr>
<tr>
<td align="left" valign="top" style="padding-left:1em">1-to-1 (occurred >1)</td>
<td align="center" valign="top"></td>
<td align="center" valign="top">66</td>
<td align="center" valign="top">67</td>
<td align="center" valign="top">54</td>
<td align="center" valign="top">24</td>
</tr>
<tr>
<td align="left" valign="top" style="padding-left:1em">Many-to-1</td>
<td align="center" valign="top"></td>
<td align="center" valign="top">16</td>
<td align="center" valign="top">14</td>
<td align="center" valign="top">20</td>
<td align="center" valign="top">11</td>
</tr>
<tr>
<td align="left" valign="top" style="padding-left:1em">1-to-Many (contain duplications)</td>
<td align="center" valign="top"></td>
<td align="center" valign="top">&#x2013;</td>
<td align="center" valign="top">&#x2013;</td>
<td align="center" valign="top">&#x2013;</td>
<td align="center" valign="top">49</td>
</tr>
<tr>
<td align="left" valign="top">Forename (1-2 char)</td>
<td align="center" valign="top">743</td>
<td align="center" valign="top">641 (&#x2212;13.7%)</td>
<td align="center" valign="top">679 (&#x2212;8.6%)</td>
<td align="center" valign="top">642 (&#x2212;13.4%)</td>
<td align="center" valign="top">687 (&#x2212;7.5%)</td>
</tr>
<tr>
<td align="left" valign="top" style="padding-left:1em">1-to-1</td>
<td align="center" valign="top"></td>
<td align="center" valign="top">555</td>
<td align="center" valign="top">608</td>
<td align="center" valign="top">557</td>
<td align="center" valign="top">600</td>
</tr>
<tr>
<td align="left" valign="top" style="padding-left:1em">1-to-1 (occurred >1)</td>
<td align="center" valign="top"></td>
<td align="center" valign="top">8</td>
<td align="center" valign="top">13</td>
<td align="center" valign="top">11</td>
<td align="center" valign="top">3</td>
</tr>
<tr>
<td align="left" valign="top" style="padding-left:1em">Many-to-1</td>
<td align="center" valign="top"></td>
<td align="center" valign="top">77</td>
<td align="center" valign="top">57</td>
<td align="center" valign="top">74</td>
<td align="center" valign="top">60</td>
</tr>
<tr>
<td align="left" valign="top" style="padding-left:1em">1-to-Many (contain duplications)</td>
<td align="center" valign="top"></td>
<td align="center" valign="top">&#x2013;</td>
<td align="center" valign="top">&#x2013;</td>
<td align="center" valign="top">&#x2013;</td>
<td align="center" valign="top">14</td>
</tr>
<tr>
<td align="left" valign="top">Full name</td>
<td align="center" valign="top">771</td>
<td align="center" valign="top">767 (&#x2212;0.5%)</td>
<td align="center" valign="top">769 (&#x2212;0.3%)</td>
<td align="center" valign="top">763 (&#x2212;1.0%)</td>
<td align="center" valign="top">770 (&#x2212;0.1%)</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<p>We also described how many names have 1-to-1, 1-to-many, and many-to-1 correspondence.</p>
</table-wrap-foot>
</table-wrap>
<p>There were 743 unique combinations of forenames in Chinese, corresponding to 641 unique Jyutping representations, and 679 Pinyin representations (<xref ref-type="table" rid="table-2">Table 2</xref>). In our data of predominantly Cantonese-based names, we observed more unique Pinyin forename combinations than Jyutping. Similar to naming clusters in other languages, Hong Kong people tend to use variations of similarly sounding names. For example, forename &#x201C;Paak3Hei1&#x201D; occurred six times, but each represented a unique Chinese forename. Pinyin would represent these six names in four different ways. In this case, Pinyin becomes more specific than Jyutping in differentiating people in our sample. We expect the specificity of Pinyin to be lower in a majority Mandarin-speaking sample, or in a larger population with more variations in names. Both Jyutping and Pinyin seem to be able to increase linkage quality in dealing with pronunciation-based errors and rare names.</p>
</sec>
<sec>
<title>Implication for linkage</title>
<p>We compared how different name encoding strategies impact on blocking. Since forename and surname combination almost uniquely identifies every individual in our dataset, we only used blocking on surnames as an example. We evaluated whether different encodings of the same surname would be put into the same block and produced recall and precision statistics based on the ground truth (Chinese surnames). Blocking based on full HKG-romanisation performed the worst in terms of recall at 68.8%, whilst both Jyutping and Pinyin (with tonal information) achieved over 95% recall, at comparable or superior precision (<xref ref-type="fig" rid="fig-2">Figure 2</xref>). Full comparison of other blocking rules is described in <xref ref-type="supplementary-material" rid="sup-a">Appendix Table 1</xref> and <xref ref-type="supplementary-material" rid="sup-a">2</xref> (<xref ref-type="supplementary-material" rid="sup-a">Appendix 2</xref>). Block rules 5,6 and 8,9 compares blocking using first two characters of Jyutping and Pinyin respectively with and without tonal information. Incorporating tonal information improved precision in both cases.</p>
<fig id="fig-2">
<label>Figure 2</label>
<caption><p>Comparison of precision and recall by blocking rules based on different romanisation systems. Blocking rules are described in detail in <xref ref-type="supplementary-material" rid="sup-a">Appendix 2</xref></p></caption>
<graphic xlink:href="ijpds-06-2935-g002.tif"/>
</fig>
</sec>
<sec>
<title>Informative missingness</title>
<p>A further promise of tonal representations of Chinese names is the potential of using tones to impute missing characters. Frequencies of tonal combinations of Jyutping and Pinyin names likely follow a Zipf&#x2019;s distribution [<xref ref-type="bibr" rid="ref-20">20</xref>], where a few combinations represent most names and a long tail of combinations have very few counts. In our sample, the top 10 tonal combinations represented 38.3% names in Jyutping and 45.0% in Pinyin (<xref ref-type="fig" rid="fig-3">Figure 3</xref>). By further incorporating vowel information, statistically estimating missing tonal information should help calibrate non-tonal romanisation systems. For example, in a 3-character name where the first 2 characters have the Pinyin tone &#x201C;2-3&#x201D; and the last character is missing, we can expect it is at least twice as likely for the third character to have a &#x201C;2&#x201D; tone than a &#x201C;4&#x201D; tone. Combining tonal information with frequency of vowel combinations for each character, we could be potentially re-encoding romanised Chinese names. Further work using a large-scale Chinese names database would contribute to this regard.</p>
<fig id="fig-3">
<label>Figure 3</label>
<caption><p>Top 10 most common tonal combinations for 3-character Chinese names, in Jyutping (bottom x-axis) and Pinyin (top x-axis). Number on y-axis corresponds to count of names with those tonal combinations</p></caption>
<graphic xlink:href="ijpds-06-2935-g003.tif"/>
</fig>
</sec>
<sec>
<title>Generalisable lesson</title>
<p>We demonstrate that both Jyutping and Pinyin are promising alternatives to representing Chinese characters, accounting for pronunciation-based errors, rare names and tonal information, compared to HKG-romanisation or non-tonal Pinyin.</p>
<p>For data linkage researchers with access to Chinese names along with HKG-romanised named, using alternative encodings such as Jyutping and Pinyin would substantially improve blocking performance. Contextual knowledge on data sources can help in choosing appropriate blocking and linkage strategies. For example, in the 1880-1990 US linkage, Chinese names in the US Census are more likely to be based on Cantonese than Mandarin. Blocking strategies based on Jyutping surnames may therefore increase efficiency of linkage by identifying more true matches, but will increase the number of missed matches, compared to Pinyin or other romanisations. As romanised Chinese names are ascribed by immigration officers in this particular setting, Jyutping will represent forenames more precisely and sensitively than Pinyin for this linkage.</p>
<p>Phonetic encodings can be used independently to deal with missing data or used to calculate probabilistic weights. We recommend including each term of the character and phonetic encoding separately to provide more flexibility in weight adjustment. The above recommendations are limited to datasets not already encoded. We are not aware of any approaches that could consistently re-encode tonal languages, especially when tonality of characters is not captured in romanised encoding. Using frequency-based methods to probabilistically assign re-encoded characters could be possible, by incorporating character position, vowels, and tonality. However, this approach may require strong assumptions on the distribution of the tones in any established dictionary to be the same as the sample. Future work should explore the feasibility and contexts in which re-encoding is suitable.</p>
<p>Developing a language-specific pre-processing and romanisation approach requires leadership and skills from people who speak these languages. We ask database owners in developing countries or former colonial regions (such as Hong Kong), where English remains the dominant language in which these databases are operating, to consider how names can be best represented and how tonal information can be retained in their databases. As for developed countries, tone-sensitive romanisation systems provide more flexibility in developing linkage strategies and could improve linkage quality for minoritised ethnic populations and migrants. Operationally, with vast advancement in voice-to-text transcription, asking individuals to say their name in their mother tongue may be a simple way to record extra information that is conducive to data linkage. This is relevant for other tonal languages, as well as character-based non-tonal languages.</p>
<p>Collecting, preserving and utilising people&#x2019;s names in their original languages, or alternatively standardised romanisation systems, is ethically and socially pertinent and may support the development of language-specific pre-processing and linkage strategies that result in more inclusive research data that better represents the targeted populations.</p>
</sec>
</sec>
<sec>
<title>Recommendations</title>
<p>For data linkage, where possible, use systematic romanisation systems (Jyutping/Pinyin) instead of non-systematic romanised systems (HKG-romanisation) to identify unique records. Phonetic encoding can potentially add benefits over non-tonal representations for blocking and linkage. Where names are only available in romanised formats, character re-encoding is possible. While such an approach has potential, it comes with strong assumptions on tone distribution that rely on established name-tonal databases for each language. We recommend analysts to develop language-specific pre-processing algorithms to enhance linkage rates for known under-represented groups.</p>
<p>For database design and management, we recommend switching to Unicode or other encoding standards to capture non-alphabetical characters. Database managers should also aim to explore database design to additionally capture tonal information and people&#x2019;s names in their original languages. This enables data linkers to apply the name romanisation method that is most appropriate for the intended linkage.</p>
</sec>
<sec sec-type="supplementary-material">
<title>Supplementary Files</title>
<supplementary-material id="sup-a">
<label>Supplementary Appendices</label> 
<media mimetype="application" mime-subtype="pdf" xlink:href="ijpds-06-2935-s001.pdf"/>
</supplementary-material>
</sec>
</body>
<back>
<ack>
<title>Acknowledgement</title>
<p>We would like to sincerely thank the reviewers for their valuable comments and suggestions which helped improve and clarify this manuscript.</p>
</ack>
<sec>
<title>Ethics statement</title>
<p>No ethics approval is required as only openly accessible data are used.</p>
</sec>
<sec>
<title>Contributions</title>
<p>JL conceptualised the project, designed, analysed and wrote up the first draft. All authors contributed to critical reviewing and revising the manuscript. All authors read and approved the final manuscript before submission and agreed with the decision to submit the manuscript.</p>
</sec>
<sec>
<title>Funding</title>
<p>This work was supported by the Wellcome Trust [212953/Z/ 18/Z].</p>
</sec>
<sec>
<title>Availability of data and materials</title>
<p>Raw name list cleaned data and codes are available on UCL Research Data Repository.</p>
</sec>
<ref-list>
<title>References</title>
<ref id="ref-1"><label>1</label><mixed-citation publication-type="journal"><string-name><surname>Harron</surname> <given-names>K</given-names></string-name>. <article-title>Data linkage in medical research</article-title>. <source>BMJ Medicine</source>. <year>2022</year> <month>Mar</month> <day>1</day>;<volume>1</volume>(<issue>1</issue>). Available from: <uri>https://bmjmedicine.bmj.com/content/1/1/e000087</uri>. <pub-id pub-id-type="doi">10.1136/bmjmed-2021-000087</pub-id></mixed-citation></ref>
<ref id="ref-2"><label>2</label><mixed-citation publication-type="journal"><string-name><surname>Doidge</surname> <given-names>JC</given-names></string-name>, <string-name><surname>Harron</surname> <given-names>KL</given-names></string-name>. <article-title>Reflections on modern methods: linkage error bias</article-title>. <source>International Journal of Epidemiology</source>. <year>2019</year> <month>Dec</month> <day>1</day>;<volume>48</volume>(<issue>6</issue>):<fpage>2050</fpage>&#x2013;<lpage>60</lpage>. <pub-id pub-id-type="doi">10.1093/ije/dyz203</pub-id></mixed-citation></ref>
<ref id="ref-3"><label>3</label><mixed-citation publication-type="website"><collab>UNGEGN Working Group</collab>. <article-title>Arabic REPORT ON THE CURRENT STATUS OF UNITED NATIONS ROMANIZATION SYSTEMS FOR GEOGRAPHICAL NAMES</article-title> [Internet]. <source>United Nations</source>; <year>2018</year>. Available from: <uri>https://arhiiv.eki.ee/wgrs/rom1_ar.pdf</uri>.</mixed-citation></ref>
<ref id="ref-4"><label>4</label><mixed-citation publication-type="journal"><string-name><surname>McGrath-Lone</surname> <given-names>LM</given-names></string-name>, <string-name><surname>Libuy</surname> <given-names>N</given-names></string-name>, <string-name><surname>Etoori</surname> <given-names>D</given-names></string-name>, <string-name><surname>Blackburn</surname> <given-names>R</given-names></string-name>, <string-name><surname>Gilbert</surname> <given-names>R</given-names></string-name>, <string-name><surname>Harron</surname> <given-names>K</given-names></string-name>. <article-title>Ethnic bias in data linkage</article-title>. <source>The Lancet Digital Health</source>. <year>2021</year> <month>Jun</month> <day>1</day>;<volume>3</volume>(<issue>6</issue>):<fpage>e339</fpage>. <pub-id pub-id-type="doi">10.1016/S2589-7500(21)00081-9</pub-id></mixed-citation></ref>
<ref id="ref-5"><label>5</label><mixed-citation publication-type="journal"><string-name><surname>Lam</surname> <given-names>J</given-names></string-name>. <article-title>Terminating bias: How Arnold Schwarzenegger showed us the importance of spelling names correctly</article-title>. <source>Significance</source>. <year>2024</year> <month>Nov</month> <day>1</day>;<volume>21</volume>(<issue>5</issue>):<fpage>36</fpage>&#x2013;<lpage>41</lpage>. <pub-id pub-id-type="doi">10.1093/jrssig/qmae078</pub-id></mixed-citation></ref>
<ref id="ref-6"><label>6</label><mixed-citation publication-type="journal"><string-name><surname>Abramitzky</surname> <given-names>R</given-names></string-name>, <string-name><surname>Boustan</surname> <given-names>LP</given-names></string-name>, <string-name><surname>Eriksson</surname> <given-names>K</given-names></string-name>. <article-title>Europe&#x2019;s Tired, Poor, Huddled Masses: Self-Selection and Economic Outcomes in the Age of Mass Migration</article-title>. <source>Am Econ Rev</source>. <year>2012</year> <month>Aug</month>;<volume>102</volume>(<issue>5</issue>):<fpage>1832</fpage>&#x2013;<lpage>56</lpage>. <pub-id pub-id-type="doi">10.1257/aer.102.5.1832</pub-id></mixed-citation></ref>
<ref id="ref-7"><label>7</label><mixed-citation publication-type="website"><collab>ONS. ONS website, methodology article, Refugee integration outcomes data-linkage pilot: Census 2021 linkage methodology</collab> [Internet]. <year>2023</year> [Accessed <day>11</day> <month>Jul</month> <year>2024</year>]. Available from: <uri>https://www.ons.gov.uk/peoplepopulationandcommunity/populationandmigration/internationalmigration/articles/refugeeintegrationoutcomesdatalinkagepilot/census2021linkagemethodologyupdate#linkage-methods</uri>.</mixed-citation></ref>
<ref id="ref-8"><label>8</label><mixed-citation publication-type="website"><collab>Office for National Statistics (ONS)</collab>, released 17 August 2023, <article-title>ONS website, statistical bulletin, Births by parents&#x2019; country of birth, England and Wales</article-title>; <year>2022</year> [Internet]. <year>2023</year> [Accessed <day>19</day> <month>Aug</month> <year>2024</year>]. Available from: <uri>https://www.ons.gov.uk/peoplepopulationandcommunity/birthsdeathsandmarriages/livebirths/bulletins/parentscountryofbirthenglandandwales/2022</uri>.</mixed-citation></ref>
<ref id="ref-9"><label>9</label><mixed-citation publication-type="journal"><string-name><surname>Postel</surname> <given-names>HM</given-names></string-name>. <article-title>Record Linkage For Character-Based Surnames: Evidence from Chinese Exclusion</article-title>. <source>Explor Econ Hist</source>. <year>2023</year> <month>Jan</month>;<volume>87</volume>:<fpage>101493</fpage>. <pub-id pub-id-type="doi">10.1016/j.eeh.2022.101493</pub-id></mixed-citation></ref>
<ref id="ref-10"><label>10</label><mixed-citation publication-type="website"><collab>Jyutping Cantonese Romanization Scheme - The Linguistic Society of Hong Kong [Internet]</collab>. <year>1993</year> [Accessed <day>19</day> <month>Aug</month> <year>2024</year>]. Available from: <uri>https://lshk.org/jyutping-scheme/</uri></mixed-citation></ref>
<ref id="ref-11"><label>11</label><mixed-citation publication-type="book"><string-name><surname>Chen</surname> <given-names>LL</given-names></string-name>. <chapter-title>Hanyu Pinyin</chapter-title>. In: <source>The Routledge Encyclopedia of the Chinese Language</source>. <publisher-name>Routledge</publisher-name>; <year>2016</year>.</mixed-citation></ref>
<ref id="ref-12"><label>12</label><mixed-citation publication-type="journal"><string-name><surname>Kataoka</surname> <given-names>S</given-names></string-name>, <string-name><surname>Lee</surname> <given-names>C</given-names></string-name>. <article-title>A system without a system: Cantonese romanization used in Hong Kong place and personal names</article-title>. <source>Hong Kong Journal of Applied Linguistics</source>. <year>2008</year>;<volume>11</volume>(<issue>1</issue>):<fpage>79</fpage>&#x2013;<lpage>98</lpage>.</mixed-citation></ref>
<ref id="ref-13"><label>13</label><mixed-citation publication-type="journal"><string-name><surname>Myers</surname> <given-names>MD</given-names></string-name>, <string-name><surname>Klein</surname> <given-names>HK</given-names></string-name>. <article-title>A Set of Principles for Conducting Critical Research in Information Systems</article-title>. <source>MIS Quarterly</source>. <year>2011</year>;<volume>35</volume>(<issue>1</issue>):<fpage>17</fpage>&#x2013;<lpage>36</lpage>. <pub-id pub-id-type="doi">10.2307/23043487</pub-id></mixed-citation></ref>
<ref id="ref-14"><label>14</label><mixed-citation publication-type="book"><string-name><surname>Stuart-Smith</surname> <given-names>J</given-names></string-name>, <string-name><surname>Cortina-Borja</surname> <given-names>M</given-names></string-name>. <chapter-title>A law unto themselves?</chapter-title> <source>An acoustic phonetic study of tonal consonants in Panjabi</source>. In: <string-name><surname>Willi</surname> <given-names>A</given-names></string-name>, <string-name><surname>Probert</surname> <given-names>R</given-names></string-name>, editors. <publisher-name>Oxford</publisher-name>: <publisher-loc>Oxford University Press</publisher-loc>; <year>2012</year>. p. <fpage>61</fpage>&#x2013;<lpage>82</lpage>. Available from: <uri>https://eprints.gla.ac.uk/70581/</uri>.</mixed-citation></ref>
<ref id="ref-15"><label>15</label><mixed-citation publication-type="journal"><string-name><surname>Christen</surname> <given-names>P</given-names></string-name>, <string-name><surname>Schnell</surname> <given-names>R</given-names></string-name>. <article-title>Thirty-three myths and misconceptions about population data: from data capture and processing to linkage</article-title>. <source>International Journal of Population Data Science</source>. <year>2023</year> <month>Jan</month> <day>31</day>;<volume>8</volume>(<issue>1</issue>). Available from: <uri>https://ijpds.org/article/view/2115</uri>. <pub-id pub-id-type="doi">10.23889/ijpds.v8i1.2115</pub-id></mixed-citation></ref>
<ref id="ref-16"><label>16</label><mixed-citation publication-type="other"><string-name><surname>Luc</surname> <given-names>W</given-names></string-name>. <article-title>pinyin-jyutping: Convert a Chinese sentence to Pinyin or Jyutping</article-title>. <year>2023</year>.</mixed-citation></ref>
<ref id="ref-17"><label>17</label><mixed-citation publication-type="website"><collab>Python.org</collab> [Internet]. <year>2024</year> [Accessed <day>9</day> <month>Dec</month> <year>2024</year>]. <article-title>Welcome to Python.org</article-title>. Available from: <uri>https://www.python.org/</uri>.</mixed-citation></ref>
<ref id="ref-18"><label>18</label><mixed-citation publication-type="website"><collab>CC-Canto &#x2013; A Cantonese dictionary for everyone</collab> [Internet]. [Accessed <day>20</day> <month>Aug</month> <year>2024</year>]. Available from: <uri>https://cantonese.org/</uri>.</mixed-citation></ref>
<ref id="ref-19"><label>19</label><mixed-citation publication-type="website"><string-name><surname>Lam</surname> <given-names>J</given-names></string-name>. <article-title>Jyutping Project - Raw Data and Clean Data [Internet]</article-title>. <source>University College London</source>; <year>2024</year> [Accessed <month>Aug</month> <day>19</day> <year>2024</year>]. Available from: <uri>https://rdr.ucl.ac.uk/articles/dataset/Jyutping_Project_-_Raw_Data_and_Clean_Data/26504347/1</uri>.</mixed-citation></ref>
<ref id="ref-20"><label>20</label><mixed-citation publication-type="journal"><string-name><surname>Newman</surname> <given-names>M</given-names></string-name>. <article-title>Power laws, Pareto distributions and Zipf&#x2019;s law</article-title>. <source>Contemporary Physics</source>. <year>2005</year> <month>Sep</month>;<volume>46</volume>(<issue>5</issue>):<fpage>323</fpage>&#x2013;<lpage>51</lpage>. <pub-id pub-id-type="doi">10.1080/00107510500052444</pub-id></mixed-citation></ref>
</ref-list>
<glossary>
<title>Abbreviations</title>
<array>
<tbody>
<tr>
<td>ABE</td>
<td>Abramitzky, Boustan, Eriksson method</td>
</tr>
<tr>
<td>HKG-romanisation</td>
<td>Hong Kong Government Cantonese Romanisation system</td>
</tr>
<tr>
<td>US</td>
<td>United States</td>
</tr>
</tbody>
</array>
</glossary>
</back>
</article>