Show Summary Details
Page of

Axial spondyloarthritis in Asia 

Axial spondyloarthritis in Asia
Chapter:
Axial spondyloarthritis in Asia
Author(s):

Huji Xu

, Feng Huang

, Chan-Bum Choi

, and Tae-Hwan Kim

DOI:
10.1093/med/9780198734444.003.0028
Page of

PRINTED FROM OXFORD MEDICINE ONLINE (www.oxfordmedicine.com). © Oxford University Press, 2020. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Medicine Online for personal use (for details see Privacy Policy and Legal Notice).

date: 29 March 2020

The prevalence of axial spondyloarthritis (axSpA) in Chinese and Korean populations is not dissimilar to that in Caucasians. However, the age of onset is younger and peripheral arthritis of the lower limb is relatively more common. Multicenter studies have revealed similarities and differences among different ethnic backgrounds. For example, the dominant HLA-B27 subtype in Chinese SpA is B2704, while it is B2705 in Koreans. Both Chinese and Korean rheumatologists have adopted ASAS/EULAR guidelines to manage axSpA. TNFi are covered by insurance in Korea but not in China. Owing to early onset and the high cost of TNFi therapy, axSpA has placed enormous burdens on both patients and society in Asia. To achieve a higher HRQoL, rheumatologists are bringing forward cost-effective and treat-to-target therapeutic strategies by integrating nonpharmacological treatment, traditional medications, and biologics in a multimodality setting. Further basic and clinical studies in Asian populations are needed to improve decision-making in clinical practice.

Access to the complete content on Oxford Medicine Online requires a subscription or purchase. Public users are able to search the site and view the abstracts for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access token, please see the token for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.