Hi Susan,
I see outpatient hospital/physician billing CPT coding as follows for
ventilation.
94656 - INITIAL VENTILATOR MGMT
94657 - CONTINUOUS VENT
94660 - NIV/CPAP/BIPAP
However, hospitals will bill for mechanical ventilation and COVID patients are
likely to be inpatient, so you could look for these ICD-10 procedure codes and
Epic sites could try using the Epic-specific SQL below.
Assistance with Respiratory Ventilation, <24 Hrs, CPAP 5A09357
Assistance with Resp Ventilation, <24 Hrs, Intermit Pos Air 5A09358
Assistance with Resp Ventilation, <24 Hrs, Cont Neg Air 5A09359
Assistance with Resp Ventilation, <24 Hrs, Intermit Neg Air 5A0935B
Assistance with Respiratory Ventilation, <24 Hrs 5A0935Z
Assistance with Respiratory Ventilation, 24-96 Hrs, CPAP 5A09457
Assist with Resp Ventilation, 24-96 Hrs, Intermit Pos Air 5A09458
Assistance with Resp Ventilation, 24-96 Hrs, Cont Neg Air 5A09459
Assist with Resp Ventilation, 24-96 Hrs, Intermit Neg Air 5A0945B
Assistance with Respiratory Ventilation, 24-96 Hrs 5A0945Z
Assistance with Respiratory Ventilation, >96 Hrs, CPAP 5A09557
Assistance with Resp Ventilation, >96 Hrs, Intermit Pos Air 5A09558
Assistance with Resp Ventilation, >96 Hrs, Cont Neg Air 5A09559
Assistance with Resp Ventilation, >96 Hrs, Intermit Neg Air 5A0955B
Assistance with Respiratory Ventilation, >96 Hrs 5A0955Z
select peh.*
from fh_clarity_etl_src.pat_enc_hsp peh
join fh_clarity_etl_src.hsp_acct_px_list hapl on peh.hsp_account_id =
hapl.hsp_account_id
join fh_clarity_etl_ref.cl_icd_px icdp on hapl.final_icd_px_id = icdp.icd_px_id
where hapl. final_icd_px_id IN ('76870', '76871', '76872', '76873', '76874',
'76875', '76865'
, '76876', '76866', '76877', '76867', '76878', '76868', '76879',
'76869')
and peh.hosp_admsn_time::date > '2020-01-01'
Best,
Kris
(414) 416-2389 (cell)
Kristen Osinski, MS
Business Analyst, Biomedical Informatics
Clinical & Translational Science Institute
Medical College of Wisconsin
[email protected] (414) 805-7245 (office)
On 5/20/20, 8:21 AM, "Gpc-dev on behalf of [email protected]"
<[email protected] on behalf of
[email protected]> wrote:
ATTENTION: This email originated from a sender outside of MCW. Use caution
when clicking on links or opening attachments.
________________________________
Send Gpc-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://urldefense.com/v3/__http://listserv.kumc.edu/mailman/listinfo/gpc-dev__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTSeWcbZA$
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gpc-dev digest..."
Today's Topics:
1. COVID CDM Data Element: Mechanical Ventilation (Susan Rea)
2. RE: Add a discussion item to GPC-dev today (05/05/2020)
(Mazumder, Narayana)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 May 2020 23:50:23 +0000
From: Susan Rea <[email protected]>
To: "[email protected]" <[email protected]>
Subject: COVID CDM Data Element: Mechanical Ventilation
Message-ID:
<dm5pr10mb17864cc3ab4f7ecb8aa9bd09ec...@dm5pr10mb1786.namprd10.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
For simplicity, I am pasting the guidance for "Use of mechanical
ventilation (Y/N)" (OBS_GEN) here:
* Binary flag to indicate whether the patient was on mechanical
ventilation during the encounter. Expected primarily for EI and IP encounters,
but may be present for ED or other encounters. Partners may need to derive
based on procedure codes or inpatient flowsheets.
* Set OBSGEN_TYPE="PC_COVID", OBSGEN_CODE = 3000 and
OBSGEN_SOURCE="DR"
* If patient was on mechanical ventilation, set RESULT_TEXT="Y"; If
it is known that the patient was NOT put on mechanical ventilation, set to "N".
Question: Are you including invasive and non-invasive ventilation? CPap,
BiPap, and intubation / bedside ventilator?
If anyone has the Charge or CPT codes they are using, that would be really
helpful.
Thank you.
Susan
Susan Rea, Medical Informaticist
Data Administrator, PCORnet Intermountain
Enterprise Analytics
Intermountain Healthcare
[email protected]<mailto:[email protected]> 801-694-6343 (cell)
NOTICE: This e-mail is for the sole use of the intended recipient and may
contain confidential and privileged information. If you are not the intended
recipient, you are prohibited from reviewing, using, disclosing or distributing
this e-mail or its contents. If you have received this e-mail in error, please
contact the sender by reply e-mail and destroy all copies of this e-mail and
its contents.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://urldefense.com/v3/__http://listserv.kumc.edu/pipermail/gpc-dev/attachments/20200519/efa22e19/attachment-0001.html__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTZS9JjyU$
>
------------------------------
Message: 2
Date: Wed, 20 May 2020 13:20:52 +0000
From: "Mazumder, Narayana" <[email protected]>
To: Xing Song <[email protected]>, "[email protected]"
<[email protected]>
Cc: Jeffrey Statland <[email protected]>
Subject: RE: Add a discussion item to GPC-dev today (05/05/2020)
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi Dr. Song,
Allina is mapping them to ICD G71.02 and we have ~45 patients.
Thanks,
Narayana
Narayana Mazumder
Research Informatics Analyst ? Lead / Data Architect
Clinical Research Informatics and Analytics
Allina Commons | 2925 Chicago Ave S | Minneapolis, MN 55407
612.262.6010 |
[email protected]<mailto:[email protected]>
From: Gpc-dev <[email protected]> On Behalf Of Xing Song
Sent: Monday, May 18, 2020 2:46 PM
To: [email protected]
Cc: Jeffrey Statland <[email protected]>
Subject: RE: Add a discussion item to GPC-dev today (05/05/2020)
Dear GPC sites,
Here is a second follow-up on the diagnosis coding question for
Facioscapulohumeral muscular dystrophy (FSHD), as we discussed in the dev-call
two weeks ago.
May I know how FSHD is codified in your system (i.e. is it coded as the
granular IMO terms, or being properly mapped to the ICD10 G71.02 code, or being
mapped to the SNOMED CT concept
(https://urldefense.com/v3/__http://bioportal.bioontology.org/ontologies/SNOMEDCT?p=classes&conceptid=399091004))*__;Pw!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTMZcnuao$
And how many FSHD patients can be identified by that corresponding codes?
The sites that I am still missing this information from are:
- MCW
- UIOWA
- Intermountain
- Allina
- MU
- UTSW
- Indiana
- Marshfield
Since we are trying to catch a LOI submission deadline and this information
is deemed to be important for the submission, we would really appreciate your
reply by the end of Wednesday (05/20/2020).
If you have already replied but I somehow missed it, please also remind me
again with your answers (and I apologize in advance for that!)
Thank you very much for sharing the information with us!
Xing Song, Ph.D.
Research Assistant Professor
Center for Medical Informatics and Enterprise Analytics
University of Kansas Medical Center
Email: [email protected]<mailto:[email protected]>
Phone: (913)-588-7605
From: Xing Song
Sent: Friday, May 8, 2020 10:31 AM
To: [email protected]<mailto:[email protected]>
Cc: Jeffrey Statland <[email protected]<mailto:[email protected]>>; Russ
Waitman <[email protected]<mailto:[email protected]>>
Subject: RE: Add a discussion item to GPC-dev today (05/05/2020)
Dear GPC sites,
I would like to follow up on the diagnosis coding question for
Facioscapulohumeral muscular dystrophy (FSHD), as we discussed in the dev-call
this Tuesday.
May I know how FSHD is codified in your system (i.e. is it coded as the
granular IMO terms, or being properly mapped to the ICD10 G71.02 code, or being
mapped to the SNOMED CT concept
(https://urldefense.com/v3/__http://bioportal.bioontology.org/ontologies/SNOMEDCT?p=classes&conceptid=399091004))*__;Pw!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTMZcnuao$
And how many FSHD patients can be identified by that corresponding codes?
Thank you very much for your reply in advance!
Xing Song, Ph.D.
Research Assistant Professor
Center for Medical Informatics and Enterprise Analytics
University of Kansas Medical Center
Email: [email protected]<mailto:[email protected]>
Phone: (913)-588-7605
From: Xing Song
Sent: Tuesday, May 5, 2020 10:08 AM
To: [email protected]<mailto:[email protected]>
Subject: Add a discussion item to GPC-dev today (05/05/2020)
Hi, GPC-dev,
We are hoping to understand how well Facioscapulohumeral muscular dystrophy
(FSHD) is coded across GPC sites. As we looked at KUMC?s data (in the forwarded
email), FSHD is coded by multiple IMO categories which have been grouped under
very general terms such as ICD9:359.1 and ICD10:71. However, there exists an
ICD10:71.02 code, which specifically capture the FSHD cohort, but not seem to
be utilized here at KUMC (and maybe similar issue applies to other GPC sites).
We want to see if any other GPC sites could have the capability to identify
the FSHD cohort either with this specific ICD10:71.02 code, or IMO categories
(as KUMC), or even SNOMED CT concept
(https://urldefense.com/v3/__http://bioportal.bioontology.org/ontologies/SNOMEDCT?p=classes&conceptid=399091004__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTUw0xVHg$
), with high sensitivity?
I actually have also logged a GPC Research Assessment Request for this,
which probably has already been broadcast to the sites.
Thank you very much!
Xing Song, Ph.D.
Research Assistant Professor
Center for Medical Informatics and Enterprise Analytics
University of Kansas Medical Center
Email: [email protected]<mailto:[email protected]>
Phone: (913)-588-7605
From: Russ Waitman <[email protected]<mailto:[email protected]>>
Sent: Monday, May 4, 2020 4:41 PM
To: Kiley Higgs <[email protected]<mailto:[email protected]>>; Xing Song
<[email protected]<mailto:[email protected]>>; Jeffrey Statland
<[email protected]<mailto:[email protected]>>; Michaela Walker
<[email protected]<mailto:[email protected]>>
Cc: Russ Waitman <[email protected]<mailto:[email protected]>>
Subject: Re: PCORI Grant- FSHD Review
Note the snomed concept exists:
https://urldefense.com/v3/__http://bioportal.bioontology.org/ontologies/SNOMEDCT?p=classes&conceptid=399091004__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTUw0xVHg$
https://urldefense.com/v3/__https://pcornet.org/pcornet-front-door/__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTrq6JYoQ$
[A screenshot of a cell phone Description automatically generated][A
screenshot of text Description automatically generated]
Then just know the basic demographics,
Larger issue how the patients do over time ( prior discussion of wheelchair)
? BMI,
? medical comorbidities ? use elements of a Charlton comorbidity
score,
? ambulatory or not (CPT code
? Which of these elements are in the CDM versus need to be collected
prospectively for the study in the registry
? The new standard minimal data set elements from the clinic tests
(and whether they cold be done via telemed) is the areas where data collection
would be needed. These clinic performance measures are often just in the
clinic note
o e.g. Timed Up and Go
https://urldefense.com/v3/__https://www.ncbi.nlm.nih.gov/medgen/754182__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTOUFx_iI$
)
o Brooke Upper Extremity Score
?
https://urldefense.com/v3/__https://www.researchgate.net/figure/Grading-for-Brooke-and-Vignos-Scales_tbl2_224053494__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTZgWb2zU$
Note the wheelchair CPT code seems to be used but underutilized. The
HCPCS are not used at UMC
[cid:[email protected]]
Russ
From: [email protected]<mailto:[email protected]>
When: 4:00 PM - 5:00 PM May 4, 2020
Subject: PCORI Grant- FSHD Review
Location:
https://urldefense.com/v3/__https://kumc-ois.zoom.us/j/92871366252?pwd=eHd5R2U5UWoyOEpDWWFJcFFJUDFpdz09__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTF4RdeiM$
Join Zoom Meeting
https://urldefense.com/v3/__https://kumc-ois.zoom.us/j/92871366252?pwd=eHd5R2U5UWoyOEpDWWFJcFFJUDFpdz09__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTF4RdeiM$
Meeting ID: 928 7136 6252
Password: 276163
One tap mobile
+12532158782,,92871366252#,,1#,276163# US (Tacoma)
+13462487799,,92871366252#,,1#,276163# US (Houston)
Dial by your location
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 408 638 0968 US (San Jose)
+1 669 900 6833 US (San Jose)
+1 301 715 8592 US (Germantown)
+1 312 626 6799 US (Chicago)
+1 646 876 9923 US (New York)
Meeting ID: 928 7136 6252
Password: 276163
Find your local number:
https://urldefense.com/v3/__https://kumc-ois.zoom.us/u/acjA6SdDXh__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTWQvOY7w$
Join by SIP
[email protected]<mailto:[email protected]>
Join by H.323
162.255.37.11 (US West)
162.255.36.11 (US East)
213.19.144.110 (EMEA)
103.122.166.55 (Australia)
69.174.57.160 (Canada)
207.226.132.110 (Japan)
Meeting ID: 928 7136 6252
Password: 276163
This message contains information that is confidential and may be
privileged. Unless you are the addressee (or authorized to receive for the
addressee), you may not use, copy or disclose to anyone the message or any
information contained in the message. If you have received the message in
error, please advise the sender by reply e-mail and delete the message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://urldefense.com/v3/__http://listserv.kumc.edu/pipermail/gpc-dev/attachments/20200520/4ef01944/attachment.html__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTdJ48ToA$
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 252899 bytes
Desc: image001.png
URL:
<https://urldefense.com/v3/__http://listserv.kumc.edu/pipermail/gpc-dev/attachments/20200520/4ef01944/attachment.png__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTvKcY_tM$
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 359791 bytes
Desc: image002.png
URL:
<https://urldefense.com/v3/__http://listserv.kumc.edu/pipermail/gpc-dev/attachments/20200520/4ef01944/attachment-0001.png__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTmPV2Z0s$
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 34174 bytes
Desc: image003.png
URL:
<https://urldefense.com/v3/__http://listserv.kumc.edu/pipermail/gpc-dev/attachments/20200520/4ef01944/attachment-0002.png__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQT0v4nScM$
>
------------------------------
Subject: Digest Footer
_______________________________________________
Gpc-dev mailing list
[email protected]
https://urldefense.com/v3/__http://listserv.kumc.edu/mailman/listinfo/gpc-dev__;!!H8mHWRdzp34!sjLafRcf1sTZx737TFQZg402MWTSM2lMq-mb4A1Q25jnaoeL8UavlOQTSeWcbZA$
------------------------------
End of Gpc-dev Digest, Vol 75, Issue 19
***************************************
_______________________________________________
Gpc-dev mailing list
[email protected]
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
