Show Summary Details
Page of

ROR2, Brachydactyly Type B, and Recessive Robinow Syndrome 

ROR2, Brachydactyly Type B, and Recessive Robinow Syndrome
ROR2, Brachydactyly Type B, and Recessive Robinow Syndrome

Andrew O. M. Wilkie

Page of

PRINTED FROM OXFORD MEDICINE ONLINE ( © Oxford University Press, 2021. 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: 27 February 2021

Mutations of the gene ROR2 (receptor tyrosine kinase-like orphan receptor 1), which maps to 9q22 and encodes a receptor tyrosine kinase (RTK) that participates in Wingless-type (Wnt) signaling, have been identified in two distinct skeletal disorders, dominantly inherited brachydactyly type B (BDB) (OMIM 113000) and recessive Robinow syndrome (RRS). This demonstrates that ROR2 is required for the development of multiple organs, most prominently bone, but including, in the case of RRS, the face, heart, and urogenital system. Genetic evidence indicates that BDB mutations act in dominant positive or negative manner, whereas abnormal intracellular processing of RRS mutations has been demonstrated indicating recessive loss of protein function. A single unlinked paralogue Ror1/ROR1 is present in mice and humans, but mutations of ROR1 have not yet been identified in any human disorder. Mutations have been identified in the WNT5A gene in affected members of a family with autosomal dominant Robinow syndrome supporting a role for ROR2 in Wnt signaling

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.