CSE External Interface Strengths and Weaknesses Worksheet
Click here to download the MS Word Format
- Purpose:
- To survey and record the perceived strengths and weaknesses separately for current CSE interfaces.
- To survey and record the need for interfaces where they do not currently exist.
- To provide a reference document to use in determining actions needed to modify or update existing interface processes to meet minimum or expected needs for the CSE organization.
- A factor would be considered a strength when it is a distinct competency that the Agency possesses. A factor would be considered a weakness when it is something the Agency does poorly or does not have the capacity to do.
- This information will be utilized in formulation of a strategy plan for CSE as a summary of interfaces needing update or replacement.
- Instructions for questions:
- Complete the following sample questions for each interface process within the CSE organization.
- Because individuals polled may have different perceptions about the strengths and weaknesses of the process, you should review several opinions of respected technical staff members and form a consensus opinion of the strengths and weaknesses.
- Augment the list of questions to fit your particular environment.
- Questions to be considered in determining the strengths and weaknesses of the interface process:
- Does the interface currently provide the expected results and transfer data accurately and dependably?
- Do you frequently have downtime as a result of technical problems?
- Is the transfer of data completed within the time limits required?
- Does your interface process have the ability to recover from failures?
- Does your interface process have the flexibility and scalability to handle anticipated expansion?
- Do you have qualified personnel to support the interface?
- Does your interface currently work with all required entities?
- Do you have interface needs with entities that you cannot currently interface with via automated systems?
- What is the main problem with the interface?
- Can you get adequate reporting from the interface process?
- Do you need additional reporting capability to verify completeness of the interface process?
- Are there a technical limitation related to your interface system?
- Is there any known system software support issues with your system?
- Do you need enhanced speed in completion of the interface process?
- Do other systems currently wait for the interface process to complete?
- Does your interface provide sufficient validity and summary reporting of transactions?
- Does the interface have Web capabilities?
- Does the interface need Web capabilities?
- Instructions for worksheet:
- Column 1 lists the external interfaces.
- Column 2 lists the CSE business function that requires the interface
- Column 3 lists the interface protocol used (e.g., Connect:Direct, CSENet 2000, and PC:VISN) and the data format (e.g., CCD+ and CTX NACHA).
- Column 4 lists the evaluation of strengths.
- Column 5 lists the evaluation of weaknesses.
- Column 6 lists the technique to determine the strengths and weaknesses, such as judgments of key decision makers or historical experience.
- Column 7 lists potential changes.
- All entities from the External Environment Data Collection Plan worksheet must be described.
- Use the CSE Interface Types Worksheet to assist you in your analysis efforts.
Example - External Interface Strengths and Weaknesses Worksheet
|
1. External Interface |
2. CSE Business Function |
3. Interface Protocol and Data Format |
4. Evaluation of Strengths |
5. Evaluation of Weaknesses |
6. Evaluation Technique |
7. Potential Changes |
|---|---|---|---|---|---|---|
|
1. Connect:Direct (C:D) to Birthing Hospitals |
Establish Paternity |
E = C:D
M = paper report |
E. Connect:Direct is fully implemented in-house.
M. Training package for hospital acknowledgement exists. |
E. Not all hospitals are using electronic interface.
M. Not all hospitals participate in acknowledgement program. |
Judgment |
E. Evaluate in-house capacity To accept additional data. M. Train hospitals on paternity acknowledgement. |
|
2. CSENet2000 to Neighboring State |
- Case Initiation - Collections |
CSENet2000 CCD+ |
E. Committed CSENet staged implementation plan |
Neighboring State Staging of CSENet implementation may not be compatible with our plan. CCD+ payment format not supported. |
Judgment |
Staged CSENet plan may require change based upon Agency goals. Support CCD+ format. |
