event

Project Update



Version Update

This section is to update end-user of the changes and defects that has been resolved which will be included in the newer version of application and will be deployed to the facilities. All Change Request (CR) approved by Jawatankuasa Semakan Change Request will be updated in the version release. Each version that has been released will be provided with quick guides in order to explain where enhancement and changes have been made to users.

Version Content Date
Version 1.3.8.4 PhIS_CPS_1.3.8.4_Release Note v1.0.pdf 21 Apr 2016
Version 1.3.8 PhIS_CPS_1.3.8_Release Note v1.1.pdf 10 Dec 2015
Version 1.2.7 PhIS_CPS_1.3.7_Release Note v1 0.docx 05 Oct 2015

 

PhIS Database Master

PhIS Database mainly consist of the following;

  1. Pharmacy Data Dictionary
    • Includes all drugs and nondrug attributes eg: Frequency List, Route of Administration, Dosage Form, Unit of Measures etc
  2. Drug Master
    • Phis Drug list includes all Ministry of Health Drug List (FUKKM), Special Approved Drug, Galenical preparations - Sterile and Non-sterile, Cytotoxic Protocols and Radiopharmaceuticals products.
  3. NonDrug Master
    • PhIS NonDrug list mainly covers all medical disposable items, implants and medical devices.

The database is currently managed by a team of pharmacist at Pharmaceutical Service Division, Ministry of Health.

Check out the updated PhIS Database Master

User Roles

In PhIS & CPS, roles are created for various job functions. The permissions to perform certain operations are assigned to specific roles. User role is carried out according designation and responsibility of activity. User Roles that include in PhIS & CPS are as below:

1) Full Based

  1. Prescriber
  2. Registration User
  3. Pharmacist
  4. Provisional Registered Pharmacist (PRPP)
  5. Pharmacist Assistant
  6. Medical Store Personnel
  7. Approval or verifiction access rights in Inventory Module
  8. Inventory Users
  9. Pharmacy Administrator

2) Pharmacy Based

  1. Pharmacist
  2. Provisional Registered Pharmacist (PRPP)
  3. Pharmacist Assistant
  4. Medical Store Personnel
  5. Approval or verifiction access rights in Inventory Module
  6. Inventory Users
  7. Pharmacy Administrator

Download the Application Form

Change Request

Change Request (CR) is a formal proposal for an alteration to the system. Any request that is different from its original specification (referred herein as the signed User Requirement Specification, signed Software Design Document and signed Change Request Specification) has to be documented and evaluated in detail.

1.         Change Request Procedure

  • Change request (CR) can be raised by facility users,  module owners pemilik modul and also PLSB system analyst.
  • Facility users will report all issues to Helpdesk where it will be logged at Connect Manage System. Only issues classified as application request will be discussed at state and MOH level.
  • PLSB Application Analyst & Support Team will extract all CR from Connect Manage System and separate the CR based on state.
  • Change Request Review Committee (JKCR) secretariat will distribute the list of CR on a monthly basis to all state liason officers.
  • Every state liason will have discussion with state champions to review all the CR before it is endorsed in Mesyuarat Jawatankuasa Pelaksana Negeri. Review session at state level advised to do on monthly basis but if not many issue, they can hold review session accordingly before the CR submission date. The output from the review session must be submitted to the JKCR secretariat before or on the date fixed by JKCR secretariat together with Borang Pengesahan Senarai CR.
  • All recommended CR from state will be reviewed by module owner and project team in terms of feasibility.
  • All CR supported by module owner will be discussed in CR Review Committee meeting for approval and set prioritization for all the approved CR.
  • PLSB will create technical specification for all CR approved by CR Review Committee meeting.
  • System Analyst will work together with module owners to verify and finalize the technical specifications for all approved CR before beginning CR development activity.
  • Rejected CR will be updated as rejected in Connect Manage system by PLSB and those issues will be closed.
  • Any changes made to the system will have version control.
  • User Acceptance Test will be conducted for every version release with module owners.
  • Once development is completed, each version will be tested at pilot facility before being deployed and used at all other facilities.  

2.         Change Request Review Activity Schedule

No

Activities

Frequency

Timeline

Remarks

1.

CR List Generation from Connect Manage by PLSB and JKCR secretariat will distribute the CR list to State

Monthly

1st Week

The list will generate based on last month request

2.

CR Review Meeting with Champions at State

Monthly

3rd Week

Propose to discuss and confirm all requests on the same month

3.

Endorsement of CR at Mesyuarat Jawatankuasa Pelaksana Negeri

Monthly/ Quarterly

1st -2nd Week

Proposed to do Monthly meeting.

Quarterly Meeting: Feb, May, Aug and Nov

4.

State Liason to submit updated CR List to JKCR Secretariat

Monthly/ Quarterly

3rd Week

Allow to submit 3 weeks before the JKCR Review Meeting

CR submission schedule: Feb, May, Aug and Nov

5.

JKCR Secretariat Consolidate CR List from All States

Quarterly

2 Week before CR Meeting

The consolidation of CR List from all states will take at least 2 weeks

6.

Mesyuarat Jawatankuasa Kerja Semakan Change Request (Module Owners)

Quarterly

1st Week of the Month

Discuss the consolidated request & review the recommendation.

Quarterly Meeting Schedule :-

Mar, Jun, Sept and Dec

7.

Change Request Review Committee Meeting (JKCR)

Quarterly

2nd Week of the Month

Quarterly Meeting Schedule :-

Mar, Jun, Sept and Dec

 

3.         All CR raised is managed by 2 types Committee at MOH level

Commitee

CR Review Committee

 

CR Review Working Committee

 

Members
  • Bahagian Pengurusan Maklumat
  • Bahagian Perkembangan Perubatan
  • Bahagian Pembangunan Kesihatan Keluarga
  • Bahagian Telekesihatan
  • Bahagian Perkhidmatan Farmasi
  • Bahagian Kejururawatan

Module Owners

TOR

1. Develop strategies, managing and monitoring CR requirements towards strengthening pharmacy business process and monitor the effectiveness of the implementation and performance of the system at all MOH facilities in line with direction of project.

2. Review, analyze, evaluate, recommend and provide report on a regular basis and presents the outcome of Change Request Review Committee and its impact on the scope, implementation schedule and cost of the project as a whole for approval to Project Implementation and Technical Committee (PITC) and the Project Steering Committee (PSC).

3. Providing technical advice related to all CR to ensure that the CR is relevant and comply with enforced MOH policies, guidelines, acts, standard operating procedures and update the documents based on the decision from Project Implementation and Technical Committee (PITC) and Project Steering Committee (PSC).

4. Develop guidelines and provide comprehensive and systematic change request management mechanism while improving the accountability of project team with continuous improvement.

5. Provide information periodically to their respective organizations regarding CR management mechanisms, terms of reference of CR Review Committee and their roles and responsibility.

1. Check all the recommended CR received from Jawatankuasa Pelaksana Negeri is in accordance with policies, standards, guidelines and circulars from Ministry of Health.

 

2. Evaluate the requirement and benefits of all recommended CR to PhIS & CPS application and also inn terms of feasibility to the system

 

3. Recommend CR to PhIS and CPS application according to priority based on operational requirement at all facility nationwide and also prepare report and present it to Change Request review Committee.

 

4. Provide technical advice on the feasibility of the change request to PhIS dan CPS application.