<?xml version="1.0" encoding="utf-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">

    <title type="text">ASHI Forums</title>
    <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/" />
    <link rel="self" type="application/atom+xml" href="http://www.ashi-hla.org/forums/atom/" />
    <updated></updated>
    <rights>Copyright (c) 2009</rights>
    <generator uri="http://www.http://expressionengine.com" version="1.6.4">ExpressionEngine</generator>
    <id>tag:ashi-hla.org,2009:10:23</id>


    <entry>
      <title>B*4402 vs 4441</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/20/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.20</id>
      <published>2009-10-15T17:40:29Z</published>
      <updated></updated>
      <author><name>Carley  Shaut PhD</name></author>
      <content type="html">
      <![CDATA[
        <p>Our lab is looking for advice on resolving the two CWD alleles B*4402/4441 for bone marrow high-resolution typing.
<br />
Using our standard methods of One Lambda HD-SSO, sometimes these alleles can&#8217;t be resolved, especially in a patient who is also either B*15 or B*40.&nbsp; 
</p>
<p>
My question: when would you rule out B*4441 by allele frequency?
</p>
<p>
1) Both alleles are CWD alleles (Cano et al. 2007), and this is our current standard for HR results.
<br />
2) The NMDP allele frequency tables show that 4402 is very common in the US (high frequency and rank), 4441 is not listed.&nbsp; However, being new to HR typing, we are nervous about using this data over the CWD standards.
<br />
3) Allele frequencies.net shows that B*4441 has the allele frequency of 0.000 for the US.
<br />
4) Literature searches and HistoCheck show that B*4441 differs from B*4402 by 2 nucleotides and 2 amino acids.
</p>
<p>
Thank you for any advice or discussion!
</p>
      ]]>
      </content>
    </entry>

    <entry>
      <title>Looking for a female to share room in the coming 35th ASHI meeting in SF</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/19/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.19</id>
      <published>2009-09-23T08:18:53Z</published>
      <updated></updated>
      <author><name>Zeying  Du MD</name></author>
      <content type="html">
      <![CDATA[
        <p>Need a female to share the hotel in the coming ASHI meeting. Please reply zdu at bsd dot uchicago dot edu
</p>
      ]]>
      </content>
    </entry>

    <entry>
      <title>Room Sharing for ASHI Meeting</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/18/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.18</id>
      <published>2009-09-03T12:19:49Z</published>
      <updated></updated>
      <author><name>John M. Hart MBA, CHS</name></author>
      <content type="html">
      <![CDATA[
        <p>Please use this post to identify room sharing opportunities at the ASHI Annual Meeting.&nbsp; ASHI takes no responsibility for arrangements made between or among meeting attendees.
</p>
      ]]>
      </content>
    </entry>

    <entry>
      <title>HD&#45;SSO technology for High&#45;Res DNA typing</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/17/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.17</id>
      <published>2009-08-18T13:30:00Z</published>
      <updated></updated>
      <author><name>Carley  Shaut PhD</name></author>
      <content type="html">
      <![CDATA[
        <p>Hello~
<br />
Our lab has adopted the One Lambda HD-SSO system as the first step to reporting high-resolution DNA typing.&nbsp; We are pleased with the results so far, but we are still gathering more information about the strengths, limits, range, and sensitivity of this system.&nbsp; When we find a resulting allele pair that does not resolve to a single Common and Well-Documented allele or allele group, we use the O.L. allele-specific MicroSSP kits. In our hands so far, ~60% of all patient samples require secondary SSP tests to resolve one or more loci; average is 1.1 SSP tests/patient - very manageable so far.&nbsp; While we&#8217;ve been having some PCR drama lately getting perfect results (due to DNA conc., well failures, dehydrated wells? etc.), we&#8217;re working through these and discussing options with the manufacturer.
<br />
~
<br />
I&#8217;m wondering how many other labs are in our same situation. Would anyone would like to communicate and share notes/experiences using the HD-SSO and allele-specific SSP reagents for HR typing??
<br />
~
<br />
Specifically, we&#8217;ve detected several allele pairs that just can&#8217;t be resolved to single CWD alleles using these reagents, and therefore must be sent out for SBT. It would be great to know about other situations like this, ones that we just haven&#8217;t run across yet.&nbsp; We&#8217;d be happy to share more about our findings.
<br />
I&#8217;d appreciate replies to the forum or via personal email.
<br />
Thanks!
<br />
Carley Shaut
</p>
      ]]>
      </content>
    </entry>

    <entry>
      <title>Bone Marrow Transplantation Histocompatibility forum&#63;</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/16/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.16</id>
      <published>2009-08-18T13:08:28Z</published>
      <updated></updated>
      <author><name>Carley  Shaut PhD</name></author>
      <content type="html">
      <![CDATA[
        <p>Is there a web forum out there that focuses on bone marrow transplantation histocompatibility, through NMDP, ASHI, or others?
</p>
<p>
Since our lab is now offering high-resolution DNA typing to support our university&#8217;s program, it would be great to connect with similar labs. Possible topics: reporting NMDP codes and CWD alleles, high-resolution typing techniques such as HD-SSO technology, and how/when to report allele groups, etc.
</p>
<p>
I&#8217;d appreciate forum responses or personal e-mails.&nbsp; 
<br />
Thanks~
<br />
Carley
</p>
      ]]>
      </content>
    </entry>

    <entry>
      <title>CPT code survey for HLA typing</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/8/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.8</id>
      <published>2009-03-17T12:36:28Z</published>
      <updated></updated>
      <author><name>Tim Stackhouse</name></author>
      <content type="html">
      <![CDATA[
        <p><i>This is an archive from the old ASHI Forum</i>
</p>
<p>
-----
</p>

<blockquote><p><b>shelman</b>
</p>
<p>
Posted: Fri Jun 06, 2008 1:36 pm
<br />
Thank you to all those ASHI members who completed the CPT typing codes survey. Here is a link to the survey results.
</p>
<p>
<a href="http://www.surveymonkey.com/sr.aspx?sm=t6WBkRMVtxCbZgKuDw2zrOfI67OCcqYt06dum7QZfVs_3d">http://www.surveymonkey.com/sr.aspx?sm=t6WBkRMVtxCbZgKuDw2zrOfI67OCcqYt06dum7QZfVs_3d</a>
</p>
<p>
All of your comments were read and discussed by the CPT codes task force. Responses are given below. Many comments were similar, so rather than responding to each comment, the responses were combined into a single response for each issue.
</p>
<p>
Responses to survey comments from the ASHI CPT Task Force:
<br />
Several questions or comments from the survey were about creation of new CPT codes for other testing. The proposal presented only addresses the HLA typing codes, but the task force is working on other proposals for antibody and crossmatching. We would like to submit proposals to the AMA for these tests as well. If you have comments, data, or references that you think will be useful, please provide it through the forum or to members of the task force.
</p>
<p>
There were also questions and comments regarding creation of CPT codes for MICA and KIR. Changing CPT codes is a labor intensive and political process. Codes for MICA and KIR will be considered after HLA typing, antibody testing and crossmatch changes have been submitted. Those proposals will most likely be considered sometime next year. Specific information in the literature (references) supporting clinical utillity and documented data on numbers of these tests performed would be appreciated by the Task force and would facilitate the process.
</p>
<p>
There were a number or comments related to the molecular codes that are used for HLA testing. The Task Force working under the premise that ALL histocompatibility specific codes should be in the histocompatibility/tissue typing section - currently 86805 – 86849. These codes would replace/eliminate the need to use any codes in the molecular section. If the coding proposal submitted is accepted by the AMA, they would be the official AMA codes specifically for HLA typing by any method. It would not be necessary to use any molecular codes because the HLA codes would include all HLA typing codes.
</p>
<p>
A couple of people thought that we should have a code for a complete typing at Class I and Class II rather than or along with locus specific codes. We thought that the current method is much more flexible, but not terribly complicated. There are more and more instances of typing for single loci or for different combinations of loci (ABDR vs ABC and DRDQ). This would allow the flexibility to bill appropriately for the loci tested.
</p>
<p>
Several comments were related to the definition of antigen resolution typing. We are defining antigen resolution typing as low resolution molecular typing or serology. The purpose of the assay is to define the antigen, in most cases for listing on UNOS. While the technology is different, the answer is essentially the same.
</p>
<p>
Intermediate resolution typing was another area of concern for a few people. This term is less well defined than high resolution or low resolution. There is no proficiency testing for intermediate resolution for this reason. It was the consensus of the task force that this should not be a separate code. It most cases, it should be coded for using antigen level resolution.
</p>
<p>
There were a number or questions and comments regarding the use of the term “high resolution typing” rather than “allele resolution typing”. We struggled with the terminology here, but ultimately decided that this term better describes the typing performed to rule out all but one common well defined allele per chromosome at each locus. All rare alleles would not need to be ruled out before the testing could be coded as high resolution.
</p>
<p>
The task force also struggled with whether DRB3/4/5 should be separate from DRB1 at antigen level and whether antigen level resolution for DQA and DPB and/or DPA were appropriate. We will continue to look at these issues.
</p>
<p>
In answer to the questions about whether to use the codes once or twice per locus, the intent of the proposal is that the codes would be used once per locus (i.e. high res typing for A2 and A33 would have one charge for the A locus)
</p>
<p>
The greatest number of comments were related to the coding for testing for a specific HLA antigen or allele by itself (disease association, drug sensitivity, or vaccine study). This proposal did NOT have a separate code for testing for a single antigen or allele, but proposed the use of the appropriate code for the locus in question. In the proposal, a request for testing for B27 antigen would use the same code that would be used to test for the B locus at antigen level resolution as part of a complete HLA type. Overall, most of those who responded to the survey (79%) agreed with this approach. However, most of the comments preferred using a separate code for single antigen or single allele testing. We will continue to consider this option.</p></blockquote>

      ]]>
      </content>
    </entry>

    <entry>
      <title>Single antigen beads antibody analysis</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/13/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.13</id>
      <published>2009-06-24T09:02:26Z</published>
      <updated>2009-06-24T11:42:01Z</updated>
      <author><name>Andrew  Lobashevsky MD, PhD, D(ABHI)</name></author>
      <content type="html">
      <![CDATA[
        <p>Hey, everyone!
<br />
Please help. I&#8217;ve been doing antibody analysis with one lambda beads for a few years. Several months ago we had noticed decreased MFI values of pos control. DTT treatment (ASHI procedure manual) significantly improved results with excellent correlation between FC/CDC XM data. The reason was presence of blocking anti-HLA and anti-idiotypic IgM. However, in almost 40% of my tests low bead counts were observed (&lt;50) making the results unreportable to clinicians. Watching the procedure in details I had revealed formation of agglutinates after 1st washing of beads/serum mixture. This resulted in probe clogging and low bead counts consequently unless agglutinates were removed mechanically. IF anybody saw something like this and had an idea(s) how to circumvent this problem I will greatly appreciate,
<br />
Thank you very much.
<br />
Andrew
</p>
      ]]>
      </content>
    </entry>

    <entry>
      <title>Greetings from Dallas</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/15/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.15</id>
      <published>2009-07-03T11:40:46Z</published>
      <updated></updated>
      <author><name>Peter  Stastny MD</name></author>
      <content type="html">
      <![CDATA[
        <p>We used to have a &#8216;Digital Discussions&#8217; forum that was quite active. I wonder if we can get it started again. Does this Bulletin Board notify people by e-mail when there are new messages that might be of interest to them? Perhaps it is available and needs to be turned on&#8230; Lets hear from you!
</p>
<p>
-Peter
</p>
      ]]>
      </content>
    </entry>

    <entry>
      <title>B&#45;cell Antiglobulin Crossmatch</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/11/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.11</id>
      <published>2009-03-18T11:31:17Z</published>
      <updated></updated>
      <author><name>Tim Stackhouse</name></author>
      <content type="html">
      <![CDATA[
        <p><i>This is an archive from the old ASHI Forum</i>
</p>
<p>
-----
</p>

<blockquote><p><b>dannyy</b>
</p>
<p>
Posted: Thu Feb 14, 2008 3:27 pm    Post subject: B-cell Antiglobulin Crossmatch     Reply with quote
<br />
Many years ago our lab played around with using AHG in the B-Cell cytotoxicity crossmatch, with mixed results. Some cells seemed to be overly susceptible to the reagent and had high cell-death backgrounds in all sera, while others did just fine. We&#8217;re planning to evaluate B-cell-AHG again, and would apprecaite hearing others&#8217; experience and advice.</p></blockquote>

<p>
-----
</p>

<blockquote><p><b>awhiteley</b>
</p>
<p>
Posted: Mon Dec 01, 2008 1:46 pm
<br />
I think the main issue with B-Cell crossmatching is the CD32 receptors and the non-specific binding of IgG by the FcgR. Does your lab already do a B-cell Flow Crossmatch?</p></blockquote>

<p>
-----
</p>

<blockquote><p><b>dannyy</b>
</p>
<p>
Posted: Wed Jan 21, 2009 1:47 pm
<br />
Yes, we perform a B-cell Flow XM, but there are some applications where our customers prefer a cytotoxicity crossmatch.</p></blockquote>

      ]]>
      </content>
    </entry>

    <entry>
      <title>Luminex PRA Ratio</title>
      <link rel="alternate" type="text/html" href="http://www.ashi-hla.org/forums/viewthread/14/" />      
      <id>tag:ashi-hla.org,2009:forums/viewthread/.14</id>
      <published>2009-06-27T14:43:05Z</published>
      <updated></updated>
      <author><name>Fadi S. Al Zayer BSc, CHT, CHS</name></author>
      <content type="html">
      <![CDATA[
        <p>Did any body try to see at what ratio of LABScreen mix beads show MFI of single antigen more than 2000? Any studies?
</p>
      ]]>
      </content>
    </entry>


</feed>