The article type of this published article was erroneously assigned as “Review”. The correct article type is “Case Report”.
The original version of this article has been updated.
Footnotes
Approved by: Frontiers Editorial Office, Frontiers Media SA, Switzerland
Publisher’s note
All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.