(Epic Story: work should be done on sub-tickets.)
As visits are added to the data model (
TRUNK-48), we know that there are going to be many different needs for visit details across implementations. For example, HL7 has evolved to having two visit segments (PV1 and PV2) with over 100 visit attributes. These could include account or billing information, patient disposition, length of stay, etc.
Rather than trying to anticipate and hardcode every possible need into the data model, we would like to add "visit attributes" to the model just as we have done with person attributes.
The VisitAttributeTypeHandler could perform functions such as:
- Optionally provide choices
- Provide input constraints - e.g., allowable pattern(s)
- Validation - e.g., for the value itself and/or allowing or preventing repeats or duplicates