Standard Operating Procedures For Incorporating Concepts Into Forms New Form Design On The Metadata Server. Introduction and purpose. - palladiumkenya/kenyametadataserver GitHub Wiki

Table of Contents

Introduction and purpose.

The purpose of this document is to outline the procedural processes for new forms development and incorporation of concepts into the forms.

Justification.

Consistent form design and incorporation of concepts into forms is eminent in the national metadata server. The KeMDSTS working groups seeks to centralize a repository for forms for the utilization by implementation partners. In this regard, standard operating procedures are required to guide the design of new forms as well as incorporation of concepts in the forms.

Metadata working group scope of work in new form design and incorporation of concepts into forms.

To ensure consistency in new form design for utilization by implementation partners.

Objective.

To establish standard operating procedures for designing new forms and incorporating concepts into forms by the metadata server forms and concepts team.

Prerequisites.

I. The metadata server forms & concepts team (FCT) should ensure proper naming convention of a form is adhered to.

II. All required fields are captured in the form.

III. Requester has submitted a form requests to the metadata server.

IV. Knowledge of which technology should be used for the form development.

Metadata Server & Terminology Services Standard Operating Procedure For New Form design and Incorporating Concepts Into Forms.

Step 1: The requester (implementation partner) should complete and submit the metadata server form development request form. The request form outlines all the request(Link ***)

Step 2: Collaboration for the form development

Step 3: clarification of the content of the form.

I. The metadata Server FCT team has drafted SOPs for requester as a guidance for review of a proposed form prior to its submission (** link for requester SOPs). This mitigates challenges emanating from forms that change.

II. Documentation for ongoing clarification should be well captured.

Step 4: Form Keys and Incorporation of Concepts Into Forms.

Concept Look-up and Mapping.

I. The working group FCT shall look up for existing concept IDs in the metadata server concept dictionary and note the the concept IDs if its an answer or question.

II. The metadata server FCT shall adopt AMPATH color coding for coding of form key data elements as well as concepts and drug identifiers.

Concept Proposal Spreadsheet.

I. The form requester shall create and submit a proposed concept spreadsheet if the form constitutes newly introduced concepts.

II. The working group FCT will use the proposed concepts spreadsheet for concepts which do not exist in the national metadata concepts dictionary. The concepts spreadsheet should include the following fields.

 1. Proposed Concept Name
 2. Proposed Concept Description
 3. Proposed Concept Datatype
 4. Proposed Concept Synonyms
 5. Proposed Concept Class

III. For any information that is not clear, the working group FCT should seek clarifications from the requester as a guidance in creating the form key.

IV. On creation of the form key, the FCT should save the form in the following format; form_name_version_yyyymmdd_form_key.doc

Step 5:Concepts checking and creation.

 1.  Concepts pertaining to the form should be checked in the metadata server.
 2. Concepts ought to be re-used as much as possible.
 3.The creation of new concepts should be a last resort. 
 4. New concepts pertaining to the requested form(s) should be created as provided in the submitted concept spreadsheet.
 5.  The working group FCT should  map the new concepts to the CIEL concept dictionary.

Step 6: Creation of form metadata.

 1. The working group FCT should ensure that form encounter type exists before the creation of the new form.
 2. Forms ought to be created using an existing or created encounter type.
 3.Relevant fields pertaining to the encounter type should be included.
 4. Encounter location for the form should be added.
 5.  Form metadata creation is done on the metadata server.

Step 7: Form schema design

 1. Schema design is applicable for form entry and Xforms development in the metadata server. 
 2.The working group metadata server data manager will build the schema design for the proposed form by adding form fields. 
 3.The  metadata server data manager will share information on the deigned form schema with the working group FCT once the schema design is done.

Step 8: Form user interface.

User interface design should be handled by the working group FCT based on the created form schema and form key.

Step 9: Form testing and publishing on the metadata server.

References.

AMPATH (2014). https://wiki.ampath.or.ke/display/forms/2014+Internal+Form+Development+Standard+Operating+Procedures+v0.04

⚠️ **GitHub.com Fallback** ⚠️