Skip to main content

View Diary: A Software Engineer's take on Healthcare.gov (145 comments)

Comment Preferences

  •  Except that the insurance front-end (2+ / 0-)
    Recommended by:
    Chi, wader

    software for enrollments and the once-a-year policy changes has been standardized for at least a decade.

    •  Except the rules have all changed (3+ / 0-)
      Recommended by:
      Oh Mary Oh, imchange, wader

      Just to pick one...you throw out all the stuff for medical history because they can't discriminate on pre-existing conditions.

    •  I suspect front-end software is not the biggest (1+ / 0-)
      Recommended by:
      waterstreet2013

      issue in their growth pains.

      Even so, the requirements for this system appear beyond standard enrollment setups that I've seen - perhaps due to political requirements going against the grain of industry common practice and (de facto or formal) standards.

      "So, please stay where you are. Don't move and don't panic. Don't take off your shoes! Jobs is on the way."

      by wader on Sat Oct 19, 2013 at 04:33:20 PM PDT

      [ Parent ]

      •  Here's Some of the Code... (2+ / 0-)
        Recommended by:
        wader, waterstreet2013

        Javascript ACA Code

        = 'Error mapping the qualify enrollment group membersException in calling SubmitCustomEnrollmentGroups service'; resources['ffe.ee.shared.exceptions.500.20009'] = 'If retrieve Plan compare/enrollment groups data service written errorException in calling RetrieveNonFaPlanReviewConfirmDetails service'; resources['ffe.ee.shared.exceptions.500.20008'] = 'If retrieve Plan compare/enrollment groups data service written errorException in calling ConfirmNonFaEnrollmentTransaction service'; resources['ffe.ee.shared.exceptions.500.20007'] = 'If retrieve Plan compare/enrollment groups data service written errorException in calling ConfirmEnrollmentTransaction service'; resources['ffe.ee.shared.exceptions.500.20006'] = 'If retrieve Plan compare/enrollment groups data service written errorException in calling RetrieveQHPPaymentPortalData service'; resources['ffe.ee.shared.exceptions.500.20005'] = 'If retrieve Plan compare/enrollment groups data service written errorException in calling RetrievePlanReviewConfirmDetails service'; resources['ffe.ee.shared.exceptions.500.20004'] = 'If retrieve Plan compare/enrollment groups data service written errorException in calling RetrieveTaxHouseholdAPTC service'; resources[
        Just a sample.  Remember, none of this is needed with Single Payer.  My Medicare card arrived a day before my 65th birthday.  I took my birth certificate into Social Security and signed the card!
        •  I wish we were complaining about a Single Payer (0+ / 0-)

          system . . .

          "So, please stay where you are. Don't move and don't panic. Don't take off your shoes! Jobs is on the way."

          by wader on Sat Oct 19, 2013 at 05:28:21 PM PDT

          [ Parent ]

        •  Bingo !! (0+ / 0-)

          None of that is needed with a data warehouse implementation.

          If you have 500 distinct conditions to be checked (or retrieved) then the DW deisgn does them in parallel.

          The shyte-code that uses hyper-complex queries ends up seeing the SQL processor do the conditions in series -- one after another for the 500 of them.

Subscribe or Donate to support Daily Kos.

Click here for the mobile view of the site