Open Access

Common origin of the anterior choroidal artery and posterior communicating artery with a concomitant aneurysm at the internal carotid artery-posterior communicating artery junction: A case report

  • Authors:
    • Hao Chen
    • Jinlu Yu
  • View Affiliations

  • Published online on: August 24, 2021     https://doi.org/10.3892/mi.2021.12
  • Article Number: 12
  • Copyright: © Chen et al. This is an open access article distributed under the terms of Creative Commons Attribution License.

Metrics: Total Views: 0 (Spandidos Publications: | PMC Statistics: )
Total PDF Downloads: 0 (Spandidos Publications: | PMC Statistics: )


Abstract

The anterior choroidal artery (AChA) is one of the main arteries, and it can exhibit several anomalies, among which is the common origin of the AChA and posterior communicating artery (PcomA); however, this is relatively rare. In the case that the AChA originates from the PcomA, it is highly uncommon for a concomitant aneurysm to develop at the internal carotid artery (ICA)-PcomA junction. The present study reports such a case. A 58-year-old female developed a headache with nausea and vomiting. Computed tomography (CT) revealed a subarachnoid hemorrhage. CT angiography and digital subtraction angiography (DSA) revealed a right ICA-PcomA aneurysm, with the AChA arising from the proximal segment of the PcomA. The aneurysm was clipped in the hybrid operating room. DSA confirmed that the aneurysm had been clipped completely, and that the PcomA and AChA had been retained. Following surgery, the patient recovered well without any sequelae. CT angiography revealed no recurrence of the aneurysm at the 3-month follow-up. On the whole, as demonstrated by the case presented herein, when the AChA and PcomA have a common origin, the AChA and PcomA should be retained during concomitant aneurysm clipping at the ICA-PcomA to prevent severe infarction complications. Surgical clipping during hybrid surgery is a suitable choice.
Something has gone wrong

HTTP Error 400

Well this is embarrassing. Something has gone wrong. Hopefully it is a transient error that will go away if you retry.

If the problem persists if you email our System Administrators letting them know what you were doing and telling them it was because:

Exception evaluating SpringEL expression: "display eq 'abstract' and dispArt.images!=null" (template: "article" - line 383, col 15)

and then they can get to work fixing it