1.

Clinic Requests an EF

2.

Implementer determines that no EF currently in production or under development adequately addresses the issues prompting the request.

3.

Implementer explores the possibility that the request can be adequately met using other strategies, including but not limited to:

a. Narrative templates and text components

b. Letters

c. Flowsheet views

4.

Determination is made that an EF will be identified from external sources or developed internally

5.

Determine EF to be used and source

• Can a CCC EF be used?

• CCC EFs should be used if available

• If no CCC EF available, check CCC regarding CCC product development plan and timetable

• EFs from other sources

• Is there an EF on the KnowledgeBank that can be adapted for use?

• Check Centricity Healthcare User Group (CHUG) web site for a similar EF

• If no suitable EF exists, formal process for requesting, designing and developing a new EF from scratch can be initiated.

6.

Clinic representatives meet with clinic to go over what is needed in EF

• What should EF look like?

• Which data show go into the flow sheet?

• What should the text translation look like?

Clinic representatives and requesting provider meet with implementer

• Use Form Request Information document to assist in design

• Gather information regarding what is needed and workflow implications

• Organize information for EF

• Gather information for text translation that will be created from EF use