Post reply

Many to Many Relationship - Healthcare Diagnosis

  • April 18, 2016 at 10:29 am

    #400036

    I am dealing with similar issue from a previous post:

    http://www.sqlservercentral.com/Forums/Topic1699788-363-1.aspx

    Working with a Patient/Diagnose cube, need to be able to slice and dice # of patients based on diagnosis on selected dates, using both ICD9 and ICD10 codes, and as many know already there is no 1 to 1 conversion between ICD9 and ICD10.

    Diag Dim

    DiagID PatientID DiagCode DOS

    1 12345 250.00 4/18/2015

    2 12345 E11.00 2/18/2016

    250.00 (icd9) and E11.00 (icd10) - (Diabetes) are one in the same, but without knowing what codes belong to what groups makes it a challenge.

    Scenario above if I was to pull a report for the past two years, I only need to count one of the records not both of them, trying different things but nothing yet

  • April 18, 2016 at 10:50 am

    #1872835

    did you already grab the General Equivilency Mapping stuff?

    https://www.cms.gov/medicare/coding/icd10/2015-icd-10-cm-and-gems.html

    your example is a great one how codes don't have exact equivelents

    in the file for ICD9 to OCD10, 250.00 maps to E11.9, right?

    250.20 seems to map to E11.00.

    [highlight="#ffff11"]25000 E119 10000[/highlight]

    25001 E109 10000

    25002 E1165 10000

    25003 E1065 10000

    25010 E1169 10000

    25010 E1310 10000

    25011 E1010 10000

    25012 E1165 10112

    25012 E1169 10111

    25012 E1310 10111

    25013 E1010 10111

    25013 E1065 10112

    [highlight="#ffff11"]25020 E1100 10000[/highlight]

    25020 E1101 10000

    25021 E1069 10000

    25022 E1100 10111

    25022 E1165 10112

    25023 E1065 10112

    25023 E1069 10111

    25030 E11641 10000

    25031 E1011 10000

    25031 E10641 10000

    25032 E1101 10111

    25032 E1165 10112

    25033 E1011 10111

    25033 E1065 10112

    25040 E1129 10000

    25041 E1029 10000

    25042 E1121 10111

    25042 E1165 10112

    25043 E1021 10111

    25043 E1065 10112

    25050 E11311 10000

    25050 E11319 10000

    25050 E1136 10000

    25050 E1139 10000

    25051 E10311 10000

    25051 E10319 10000

    25051 E1036 10000

    25051 E1039 10000

    25052 E11311 10111

    25052 E11319 10111

    25052 E1136 10111

    25052 E1139 10111

    25052 E1165 10112

    25053 E10311 10111

    25053 E10319 10111

    25053 E1036 10111

    25053 E1039 10111

    25053 E1065 10112

    25060 E1140 10000

    25061 E1040 10000

    25062 E1140 10111

    25062 E1165 10112

    25063 E1040 10111

    25063 E1065 10112

    25070 E1151 10000

    25071 E1051 10000

    25072 E1151 10111

    25072 E1165 10112

    25073 E1051 10111

    25073 E1065 10112

    25080 E11618 10000

    25080 E11620 10000

    25080 E11621 10000

    25080 E11622 10000

    25080 E11628 10000

    25080 E11630 10000

    25080 E11638 10000

    25080 E11649 10000

    25080 E1165 10000

    25080 E1169 10000

    25081 E10618 10000

    25081 E10620 10000

    25081 E10621 10000

    25081 E10622 10000

    25081 E10628 10000

    25081 E10630 10000

    25081 E10638 10000

    25081 E10649 10000

    25081 E1065 10000

    25081 E1069 10000

    25082 E1165 10112

    25082 E1169 10111

    25083 E1065 10112

    25083 E1069 10111

    25090 E118 10000

    25091 E108 10000

    25092 E1165 10112

    25092 E118 10111

    25093 E1065 10112

    25093 E108 10111

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply