Issue 1827:  HNE does not have a list of required person traits for a person addition                                                                                                                               (pids-rtf2)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: 3. HNE does not have a list of required person traits for a person addition.  It requires that a certain number of primary, secondary, and/or tertiary person traits are defined.  It tries to match the trait definitions to a "Use Case" and will not add a person unless the list of defined traits synchs up with at least one of the "Use Cases".
  
 

Resolution: 
Revised Text: 
Actions taken:
August 18, 1998: received issue
February 25, 1999: closed issue
Discussion: 

End of Annotations:=====
3. HNE does not have a list of required person traits for a person
addition.  It requires that a certain number of primary, secondary,
and/or tertiary person traits are defined.  It tries to match the
trait definitions to a "Use Case" and will not add a person unless the
list of defined traits synchs up with at least one of the "Use Cases".
 
For example, one use case may require that three primary person traits
(such as MRN, and Name) and a secondary trait be passed before a
person may be added.

Will we be "PIDS compliant" if we don't implement the "RequiredTraits"
exception isn't used?

Under the present conditions, HNE can only return an exception that
indicates that there weren't enough traits passed to match a "Use
Case".  HNE presently doesn't have the ability to specify which traits
to pass.  The client programmer must be familiar with the HNE "Use
Cases" to know what inputs to require.