Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Medical Billing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    RE: Medical Billing

    Bill,

    I have the HIPAA book sitting on my desk, still as confused as ever. I have very simple transactions, and it seems as though whoever made up these loops has decided to make it as tough as possible.

    Tom

    Comment


      #32
      RE: Medical Billing

      Tom,

      At your convience, can you help me with a burning issue?

      I'm used to working with dbf files, fixed length records etc. The examples in the HIPAA implementation guide, show output records that are field or "element" (HIPAA speak)delimited with a character. We think we'll use "?" for element delimiter, as we find "*" in some of our policy numbers. Additionally, there is a segment terminator, "~" that terminates the segment or record.

      The examples in the implemenation guide, show all of these records simply ran together, with, of course, the segment terminator telling the receiving system where the "record" breaks are. My limited testing to this point, has been to create a blank dbf file, a single field, of some length, yet to be determined, and simply append the data as it is required in the ANSI format to this file, export it to a text file and transmit.

      This methodology creates seperate records within the dbf file and the resulting text file. Any guesses as to whether or not that would work? Any other thoughts toward this issue, even if they are simply questions, would be deeply appreciated.


      Sincerely, at your convience. And yes the IG has been on my desk all day today!


      Bill

      Comment


        #33
        RE: Medical Billing

        Tom,

        As always, as soon as I hit send, something comes to mind. After creating my dbf file, and could read it and trim and concatenate the records.

        I'm stumbling a little with what exactly the file "looks" like that we'll be sending. Not from the record format basis, all I have to do to get that is read the implementation guide (looks like a blast). But once I get the records into this transmission file what will it be like?

        Any ideas? or samples?


        Bill

        Comment


          #34
          RE: Medical Billing

          Bill,

          I got an e-mail with an atachment from Peter Wayne for a test of his HIPAA submission. It looks like there is NO cr/lf anywhere in the data. Records types are separated by the "~" character. I haven't quite figured out how to do that, yet.

          My problem is even more basic. I have a very simple recurring transmission that we do every month. We bill Medicaid for case management for Homecare Clients. Prior ro HIPAA, there were 3 records per client: Detail Header, Detail, and Detail Footer. All pertinant information was held in these threee SMALL records.

          I am so confused as to what record types I need to use for this one (what used to be) very simple transaction. New Jersey Medicaid has set an October 16 date for HIPAA compliance. This is now becoming critical. We bill $40k per month.

          Tom

          Tom

          Comment


            #35
            RE: Medical Billing

            Tom

            I can't help with the HIPAA issue, but getting data separated with a ~ is actually very easy. Just create a crlf() delimited string and then use stritran() to replace the crlf() with a ~. From the interactive window

            str = "Data"+crlf()+"more_data"
            ?str
            = Data
            more_data

            ?stritran(str,crlf(),"~")
            = "Data~more_data"

            Jerry

            Comment


              #36
              RE: Medical Billing

              Thanks, Jerry,

              I have no problem getting the tilde into the records, the problem comes when, after having built an ascii file with crlf delimited records, how do I remove the crlf???

              Tom

              Comment


                #37
                RE: Medical Billing

                I have tried emailing hendrik but have had no reply.

                residing in South Africa, I was not particulalry interested in the Medical Billing problem but am interested to see if anyone has an Optometric Package developed in A5V5.

                Of extreme importance is whether you track line items on each incoice for debtor purposes.


                Regards
                Steve

                Comment


                  #38
                  RE: Medical Billing

                  Tom,

                  You would be better off posting technical questions in the
                  Alpha Five forum.

                  Comment

                  Working...
                  X