Home › Forums › implementation › Implementation discussion ›

Minor naming annoyances

Submitted by Guest on Sun, 07/10/2012 - 11:35
in

There are a couple of minor naming/labeling problems which I as a newcomer to OPV found confusing.

1. Workflow-Sheduling: In the 'Highlight' pulldown, 'Event Type' should be 'Appointment Type'. [I was trying to figure out how to set the colour for an 'event'. The light dawned when I realised that I was selecting appointment types, not event types.]

 

2. Product Type and Class.  In some product screens there is a confusing use of the word 'type' rather than say 'class'.   Products must be in one of the three built-in 'classes', Medication, Service and Merchandise; products can be assigned to one, one or more 'Product Types'.

Where a 'class' is being referred to it should always be labeled as 'Product Class' (not 'Product Type' as at present). 
 Problem screens:
 a) The New Product popup window, which asks "Select the type of Product to create:" - this should be "Select the class of Product to create:".
 b) The Product Information Search screen, which has a column labeled "Type" - this should be "Class".

[Again, this is only a problem for a newcomer, but I found it confusing until I understood what was meant.]

‹ Label text in product definition and macros productPrice.markup functionally not used - True? ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Minor naming annoyances

Submitted by bencharlton (not verified) on Thu, 11/10/2012 - 15:34.

Its semantics, but actually its not a class its an archetype...and you can have

 Medications, Services, Merchandise, Price Template or Template.

There is a seperate Classifications for products using the word class would become confusing. Also some people use the AVPVMA classifications system as found in the shared resources.  Its really hard to come up with a naming convention here that makes sense (unless you use archetype which makes sense to implementers but not users)

Ben

 

Re: Minor naming annoyances

Submitted by tanderson on Tue, 16/10/2012 - 13:28.

The Event Type label is coming from the archetypes, so you can change it to whatever you like.

Alternatively, I can change it if there is consensus as to what it should be.

In both entity.organisationScheduleView and entity.organisationWorklistView, there is:

         <node name="highlight" path="/details/highlight" type="java.lang.String" minCardinality="0" defaultValue="'EVENT_TYPE'">
              <assertion name="lookup.local">
                  <propertyList name="entries">
                      <property name="EVENT_TYPE" value="Event Type"/>
                      <property name="CLINICIAN" value="Clinician"/>
                      <property name="STATUS" value="Status"/>
                  </propertyList>
              </assertion>
        </node>

For entity.organisationScheduleView "Event Type" could be changed to "Appointment".

For entity.organisationWorklistView it could be changed to "Task".

-Tim

Syndicate content