whbb

In your statement "Meditech allows user w/o any warning", this depends on how the facility set up the calculation to work, not Meditech.  The facility must add the warning to the calculation.  You most likely need to evaluate how the calculation is set up, and possibly the ACCESS Dictionary.
 
Here is how we set up the Calculation in Meditech:
Triger Tests:  ORD=Y, Res=Y, NP=N, ND=Y, QNS=N.  If you answer "Y" for NP (No Print) or QNS, these results of "Y" are used as part of the calculation. 
 
In the Truth Table, this is the logic we used:
IF{'X [bbk err msg]("Invalid blood type calculation.")},
X;
 
Also be sure that your truth table is set up correctly.  I made a spreadsheet of every possible result, and then created a Blood type outcome for each type.  That is ~30 different combinations to create all of the blood types for an adult (w/o DU testing).  For example, you may allow users to use A,B, but it is not required.  To report an adult OPOS blood type, the truth table would be set up like this:
Anti-A NEG
Anti B NEG
Anti-A,B NOT POS (user can answer NEG or NOT Done, but not POS)
ANTI-D POS
RHCONT NOT POS
A CELL POS
B CELL POS
 
There are four(4) possible combination of results that are allowed to create a blood type of O POS.
 
In the Access Dictionary, OVERRIDE BLOOD TYPE CALC MISMATCH?  is answered "Y".  If your forward type did not match your back type (eg. pt has anti-M causing A or B cell to be positive, but is neg when antigen neg A or B cell is used for typing), user would enter actual results, and at our facility we add comment as to what was performed to verify result.  The user can then manually enter the blood type that should be reported and blood type is accepted.  This will appear on the "Override Warning Report".
 
You also have the choice of entering the "corrected" value for the A or B cell as a result and entering a comment as to what the original result was and why it is different (Antigen neg cell used).  This way, the calculation will not have a mismatched outcome.  I wouldm't recommend this, but it could be used.  This action would not appear on the override warning report.
 
If this is answered "N", the user will not be able to define a blood type when there is a mismatch.
 
Our facility is comfortable with BBKers performing this function because of their excellent training.  Some facilities may feel that only the supervisor should enter these "mismatched" results.  In that case, I would resort to downtime and issue "O" until the blood type can be entered by supervisor.  I would never have an invalid blood type be an acceptable blood type used in the system.

I am on the Magic version5.6.6, but the Nomenclature Map was used to enter an IMO (Intelligent Medical Objects) mapping.  This will be used for EHR (Electronic Health Record).  In the Magic Version, this is on page 1 of the Product Dictionary

We use a rule that gives the user  just a warning.  In the event that the BB needed to provide a product w/o the marker, we wanted to have the option to override.  This can also be set up as a "hard stop" if you want.  How we applied this was to enter this as an assignment/issue rule for PC on page 4 of the Product dictionary.  You need to create the rule in LIS Shared Dictionaries, Rule Dictionary and create a BB assignmnet rule type.  Go to Atlas and enter "Lab Rules"  and you should be directed to the Rules Catalog that provides examples of how to create different types of rules in Meditech for Lab.
 
 
;Marker Rule is used to flag patients that require specific blood
;requirements ie, HLA matched platelets, CMV negative blood.
;Marker Rule resides in the Product Dictionary.
;Marker applied to PATIENT must be the same marker applied to PRODUCT.
;
[f bpt unit mkrs comp]^X,
IF{X "Pt marker not on unit: "_X_" OK? "^X,
[f basn yes/no](X);
[f basn ok]};

We use a rule that gives the user  just a warning.  In the event that the BB needed to provide a product w/o the marker, we wanted to have the option to override.  This can also be set up as a "hard stop" if you want.  How we applied this was to enter this as an assignment/issue rule for PC on page 4 of the Product dictionary.  You need to create the rule in LIS Shared Dictionaries, Rule Dictionary and create a BB assignmnet rule type.  Go to Atlas and enter "Lab Rules"  and you should be directed to the Rules Catalog that provides examples of how to create different types of rules in Meditech for Lab.
 
 
;Marker Rule is used to flag patients that require specific blood
;requirements ie, HLA matched platelets, CMV negative blood.
;Marker Rule resides in the Product Dictionary.
;Marker applied to PATIENT must be the same marker applied to PRODUCT.
;
[f bpt unit mkrs comp]^X,
IF{X "Pt marker not on unit: "_X_" OK? "^X,
[f basn yes/no](X);
[f basn ok]};

We use Meditech with BCTA (bar coding at the bedside).  We use the hospital id band (has a barcode).  When the user scans the barcode, if it is not for that patient, it will not allow scanning, and the RN should return the product to the blood bank.  We require a second separate draw on any non-type O patient prior to a red cell transfusion to confirm the blood type if we do not have a previous type type history.
 
We have been using this for more than 2 years, and it has been working great without a separate blood band.

I am actually scheduled to work exclusively in BB.  It is very important to have one or more regular employees dedicated in the department because of the complexity of the work.  It also gives the generalist who may rotate through BB another contact in case they need advice or help.  The one thing that I can point to that other generalists working in the Lab do not have is the sense of "ownership" that I have working in BB.
 
I have been given my own list of duties that I am responsible for to help maintain the department.  There is no "wait for the next guy to do it" because it is MY responsibility.  I have other supervisors tell me that my supervisor is lucky to have me because he doesn't have the lack of commitment from the generalists that they do.
 
Why not give generalists responsibilities?  If every Tech had "ownership" of certain tasks, perhaps there would be an opportunity for more committment from the employees.  How about assigning one generalist to maintain one instrument?
 
Just a thought... 

If you are using Meditech, on page 3 of the Product dictionary, you are going to have to create an ORDER GROUP for the RETYPE test and enter the name of that order group under "Non-Affiliated Source".  Also on page 3, for products requiring a confirmation to be performed, the "Default Blood Type" needs to be answered as "U" unknown.  On page 1 of the Product dictionary, "Typing Required?" should be answered as "Y".  Now when this product is entered into inventory, users will need to perform the retype test on the unit that is defined in your Order Group prior to use.  You need to set these up "backwards" in order to create the Order Group. 
1)  create the component T-Tests for your Group Type test for your retype "RETYPE".  Ex: anti-A unit, anti-B unit, anti-D unit (anti-A,B unit).
2)  create your B-Type Calculation for your RETYPE Blood Type (RTYPE)
3)  create the G-Type Test using your component tests and blood type tests (RETYPE)
4) create the Order Group  (BBRTYPE)
***Order Type:  ADD
***Spec Type:  NEW
***Coll Date:  T
***Time:  N
***Priority:  R
***Received?:  Y
***Recv Date:  T
***Time:  N
***BBK Test:  RETYPE
5)  Enter the retype order group on page 3 of product dictionary non-affiliated source:  BBRETYPE
Every defined product that requires a retype will need to have "BBRETYPE" added on page 3 of Product Dictionary.
 
To perform the retype test, find the specimen associated with the retype order for that product, users can enter "BU#" (blood unit number) and then scan the unit number and the retype order for that product will be there for resulting.  Once the product has been retyped, the blood type when turn from "unknown" to the confirmed blood type performed.