Percutaneous endoscopic gastrostomy (PEG) tube placement by an emergency general surgery service: Long-term follow-up is lacking

Robert W. DesPain; William J. Parker; Angela T. Kindvall; Eric A. Elster; Elliot M. Jessie; Carlos J. Rodriguez; Matthew J. Bradley

Percutaneous endoscopic gastrostomy (PEG) tube placement by an emergency general surgery service: Long-term follow-up is lacking

Robert W. DesPain^*, William J. Parker, Angela T. Kindvall, Eric A. Elster, Elliot M. Jessie, Carlos J. Rodriguez, Matthew J. Bradley

^*Corresponding author for this work

Research output: Contribution to journal › Short survey › peer-review

Original language	English
Pages (from-to)	E323-E325
Journal	American Surgeon
Volume	85
Issue number	7
State	Published - 2019
Externally published	Yes

Cite this

@article{3bf441d7fe59452cb9971c7bba475bb4,

title = "Percutaneous endoscopic gastrostomy (PEG) tube placement by an emergency general surgery service: Long-term follow-up is lacking",

author = "DesPain, {Robert W.} and Parker, {William J.} and Kindvall, {Angela T.} and Elster, {Eric A.} and Jessie, {Elliot M.} and Rodriguez, {Carlos J.} and Bradley, {Matthew J.}",

year = "2019",

language = "English",

volume = "85",

pages = "E323--E325",

journal = "American Surgeon",

issn = "0003-1348",

publisher = "SAGE Publications Inc.",

number = "7",

}

TY - JOUR

T1 - Percutaneous endoscopic gastrostomy (PEG) tube placement by an emergency general surgery service

T2 - Long-term follow-up is lacking

AU - DesPain, Robert W.

AU - Parker, William J.

AU - Kindvall, Angela T.

AU - Elster, Eric A.

AU - Jessie, Elliot M.

AU - Rodriguez, Carlos J.

AU - Bradley, Matthew J.

PY - 2019

Y1 - 2019

UR - http://www.scopus.com/inward/record.url?scp=85071468767&partnerID=8YFLogxK

M3 - Short survey

C2 - 31405433

AN - SCOPUS:85071468767

SN - 0003-1348

VL - 85

SP - E323-E325

JO - American Surgeon

JF - American Surgeon

IS - 7

ER -

Percutaneous endoscopic gastrostomy (PEG) tube placement by an emergency general surgery service: Long-term follow-up is lacking

Fingerprint

Cite this