Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Gliffy
sizeL
nameorder_type_class_map
alignleft
version1
  • order_type_class_map_id – autonumber primary key
  • concept_class_id – a reference to a concept class
  • order_type – a reference to a Java class of type ? extends Order

...

Under a "Concept Class Mappings" section of Orders Administration in the application, we would provide a way for administrators to edit and define new mappings of concept classes to order types.  For example, they would see a list of known order types by name (e.g., "Drug", "Test", "Referral", etc.) – each one corresponding to a class of type ? extends Order within the API or provided by a module.  Alongside each type of order, the administrator could enter 0-to-n concept classes that should map to that order type.  A concept class would not be required to be an order type (most classes, like Question or Misc, would not be orders) and any given concept class could only be associated with a single order type (e.g., you would not be allowed to associate the concept class "Drug" with multiple order types).

Wiki Markup
{mockup

...

:Order Type Management 1

...

|1|l|600}

This mapping accomplishes several of our requirements (and more) in a straightforward manner:

...