Billing rights don't by default involve editing demographic data, from
what I remember. That ACL profile can be changed pretty easily.
> Found manage procedure item in the reporting submenu, not easy to
> find.
Sorry -- I'm open to suggestions about where to put that management screen.
> Added new procedure, however it wouldn't show in the procedure list
Can you check to make sure it's not throwing a database error in the error.log?
--
Thanks,
Jeff
(je...@freemedsoftware.org)
FreeMED Software Foundation, Inc
http://freemedsoftware.org/
--
You received this message because you are subscribed to the Google Groups "FreeMED Support" group.
To post to this group, send email to freemed...@googlegroups.com.
To unsubscribe from this group, send email to freemed-suppo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/freemed-support?hl=en.
True -- the chances are that we're missing some stock ACL data.
When you say it doesn't show up in "the list", are you referring to
the list of procedures? Please check to see whether it is showing up
in the procrec table -- it might just be a display/refresh issue.
> Facility screen missing POS code dropdown field (11 -office, 12 - home
> etc..)
That was an issue in the interface definition for FacilityModule. I
fixed it in rev 6093, please update.
( Issue was in http://svn.freemedsoftware.org/freemed/trunk/ui/gwt/src/main/webapp/resources/interface/FacilityModule.module.xml
)
The module indexing process loading the ProcedureModule module produces that.
You can manually load it by SOURCE-ing data/schema/mysql/procrec.sql
from a MySQL console. If there's some sort of nasty error, it could
explain why the table hasn't been properly created.
--
Thanks,
Jeff
(je...@freemedsoftware.org)
I see the issue.
Run:
./data/source/cpt/download-and-prepare.sh
which should download all of the fee schedule files which this depends upon.
Yes.
> Now I can add procedures and see them in the patient procedure list, however
> when I go to Remitt Billing I don't see any entries listed to be billed.
They were added with the appropriate payers, and were set to be billable, etc?
> Question: Do I need to configure payer Remitt Assignments ( like
> paper/electronic formats ans target options) before I'll be able to see the
> billing list?
I believe so. You can use the tool/utility which allows bulk
assignments to be made if you don't want to edit every one of them by
hand.
> Question: Do I need to have Remitt running to be able to fill out remitt
> assignments?
Yes, unless you use the utility. It populates the listboxes with that
information.
(By the way, if it makes any difference, many different FreeMED
systems can share a single REMITT server, so long as each instance of
FreeMED has a separate "user" created in REMITT.)
For the AccountsReceivable screen, it's
org.freemedsoftware.api.Ledger.AgingReportQualified (can be found in
lib/org/freemedsoftware/api/Ledger.class.php), and for the
ClaimsManager screen it's
org.freemedsoftware.api.ClaimLog.AgingReportQualified (can be found in
lib/org/freemedsoftware/api/ClaimLog.class.php).
Sorry -- I think that's my fault. Just committed a fix to reenable the
REMITT billing page, although I believe we're supposed to bill from
the Claims Manager rather than directly from the REMITT billing
screen. (I believe the workflow is to select a batch of claims and hit
"Bill", although you should also be able to do it now from the REMITT
page)
Generally those data scripts can be run in any order, but they should
be run before the initial install.
> What is the correct number of tables for the last revision of freemed
> 9 ?
These are all of the pieces which are loaded from external files (so
they would all need to exist for everything to load properly):
$ fgrep LOAD data/schema/mysql/*
data/schema/mysql/cpt_source.sql:LOAD DATA LOCAL INFILE
"data/source/cpt/extract/PPRRVU09.csv"
data/schema/mysql/cpt_source.sql:LOAD DATA LOCAL INFILE
"data/source/cpt/extract/OPPSCAP.csv"
data/schema/mysql/cpt.sql:LOAD DATA LOCAL INFILE "data/source/cpt/PPRRVU.csv"
data/schema/mysql/growthcharts.sql:LOAD DATA LOCAL INFILE
"data/source/growthcharts/bmiagerev.csv"
data/schema/mysql/growthcharts.sql:LOAD DATA LOCAL INFILE
"data/source/growthcharts/hcageinf.csv"
data/schema/mysql/growthcharts.sql:LOAD DATA LOCAL INFILE
"data/source/growthcharts/lenageinf.csv"
data/schema/mysql/growthcharts.sql:LOAD DATA LOCAL INFILE
"data/source/growthcharts/statage.csv"
data/schema/mysql/growthcharts.sql:LOAD DATA LOCAL INFILE
"data/source/growthcharts/wtage.csv"
data/schema/mysql/growthcharts.sql:LOAD DATA LOCAL INFILE
"data/source/growthcharts/wtageinf.csv"
data/schema/mysql/growthcharts.sql:LOAD DATA LOCAL INFILE
"data/source/growthcharts/wtleninf.csv"
data/schema/mysql/growthcharts.sql:LOAD DATA LOCAL INFILE
"data/source/growthcharts/wtstat.csv"
data/schema/mysql/icd10.sql:LOAD DATA LOCAL INFILE
"data/source/icd-10-cm/icd10.psv"
data/schema/mysql/icd10.sql:LOAD DATA LOCAL INFILE
"data/source/icd-10-cm/icd9to10crosswalk.psv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE "data/multum/icd_9.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/multum_combination_drug.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/multum_dose_form.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/multum_drug_id.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/multum_product_strength.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/multum_route.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/multum_units.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/ndc_active_ingredient.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/ndc_active_ingredient_list.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/ndc_brand_name.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/ndc_core_description.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/ndc_ingredient_strength.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/ndc_main_multum_drug_code.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/ndc_orange_book.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE
"data/multum/ndc_pregnancy_category.csv"
data/schema/mysql/multum.sql:LOAD DATA LOCAL INFILE "data/multum/ndc_source.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE "data/drugs/ndc_listings.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE "data/drugs/ndc_packages.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE
"data/drugs/ndc_formulations.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE
"data/drugs/ndc_applications.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE "data/drugs/ndc_firms.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE "data/drugs/ndc_routes.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE
"data/drugs/ndc_dosage_form.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE "data/drugs/ndc_tbl_dosage.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE "data/drugs/ndc_tbl_route.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE "data/drugs/ndc_tbl_unit.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE "data/drugs/ndc_schedule.csv"
data/schema/mysql/ndc.sql:LOAD DATA LOCAL INFILE
"data/drugs/orangebook_products.tsv"
data/schema/mysql/npi.sql:LOAD DATA LOCAL INFILE "data/source/npi/npi.csv"
data/schema/mysql/pqri.sql:LOAD DATA LOCAL INFILE
'data/source/pqri/2009_PQRI_SingleSource_PUBLIC_CodeMaster_120808.csv'
Jeff
is it possible to reduce the height of the menu items on the left side of the screen? to eliminate the need to scroll down the browser?
It's a CSS issue -- I have to take a shot at it with firebug to correct that.
The developers who were working on the project did a great job making
a nice looking UI, but used older CSS and HTML tricks to do things
that are much easier now with newer revs of CSS and HTML5 features ...