Show Summary Details
Page of

Cost-of-illness and economic evaluations in axial spondyloarthritis 

Cost-of-illness and economic evaluations in axial spondyloarthritis
Cost-of-illness and economic evaluations in axial spondyloarthritis

Annelies Boonen

Page of

PRINTED FROM OXFORD MEDICINE ONLINE ( © 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 September 2020

Consideration of costs and budgets plays an increasingly important role in decisions on access to innovative technologies. When clinicians want to influence such decisions, it is essential to understand the information on the burden of the disease and the evidence on cost-effectiveness of technologies. This chapter provides guidance to understanding the key methodological principles of economic evaluations, and describes available evidence on these issues in axial spondyloarthritis (axSpA). In the prebiologics era, the cost-of-illness for society of ankylosing spondylitis was slightly lower than for rheumatoid arthritis, and substantially lower than chronic low back pain. Cost of sick leave and work disability accounted for up to 75% of total cost-of-illness. Treatment with biologics increased cost-of-illness substantially, but the important gain in quality-adjusted life years resulted in acceptable cost-effectiveness in patients with active disease. There remains a gap in knowledge about the cost-effectiveness of diagnosing and treating axSpA earlier.

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.