It has been almost a year, my blog is not updated .
C-HEtS phase II is still in progress. I’ve seen the prototype. Some changes has been made as per request by the domain expert user. Expexted to roll-out in Feb 2010.

The modules are:
i. Patient portal – patient can login to the application from home to view their details.
ii. Radiology & image information system
iii. Drug request
iv. Laboratory request
v. Radiology request
vi. Procedure request
vii. Rehabilitation request
viii. Diet request
ix. Nursing request
x. Social worker request

Process of integration: Currently doing negotiation with the respective vendor. It may use HL7 or may not, depend on cost and readiness of the respective vendor.  This will include integration with existing laboratory and pharmacy system. Integration of our radiology & image information system with PACS is 98% completed, using DICOM & HL7 standard.

We are planning to implement full patient accounting system (from billing until trial balance: end-to-end) on 1st of Jan 2010.

Phase III C-HEtS is expected to start in Middle of 2010. The scope will includes:
i. Nursing documentation
ii. Clinical documentation
iii. Laboratory Information System
iv. Teaching & Learning System
v. Research

From NST (09/09/2008): http://www.nst.com.my/Current_News/NST/Tuesday/National/2344766/Article

………Also launched yesterday was Phase II of the C-HEtS, the in-house information system in PPUKM.

The first phase, built in 2004 and completed in 2006, dealt with modules such as patient registration, emergency admissions, discharge and transfers, and administration of operating theatre schedules.

Following its success, Phase II will see the development of modules for the radiology information system, which include the Computerised Physician Order Entry, patient portal and integration of the C-HEtS with the old system.

The radiology department had already phased out film for scanning since August, when doctors could access the patients’ record online.

“We cut down on a lot of film as CT scans and MRI use four to five films each. For patients who request for their scan data, we provide it in a compact disc and charge them accordingly,” said Dr Lokman

This tutorial ia based on my previous posting. It is modified for JDeveloper 11g.

Download practice_for_jee5_revision_11

I’ve created a tutorial on how to develope JEE5 application. EJB 3.0 (stateless session bean) is used as business tier, ADF data model as model layer and ADF Faces as view layer. The tutorial is adapted from Appendix A, Practice & Solution , Oracle AS 10g R3: Build J2EE Applications 1.

Download tutorial (V 1.1)

If you find any error or bugs, please e-mail me or leave a comment.

Thank you

After a long discussion, finally we have come out with a solution of what JEE components we will choose for our next project phase. Here are the combinations:

Persistence layer: JDBC & Plain SQL
Business layer: Stateless session bean (EJB 3.0)
Model layer: ADF Model layer
View layer: JSF (ADF Faces)

We feel, this the best combination for us, considering all the factors that may contribute to the application development.

Much of what we need can be handled declaratively through the various bindings and use of expression language. However, it is inevitable that you will need to write code that will interact with the bindings, either in the form of:
i)Accessing (read & set) bound data values and ii)Manually executing operations and method…….Please download to read the rest.

Download
 

I’m currently developing J2EE application for my organisation. But now, I’m still evaluating the technology for business layer. Between Plain Old Java Class, EJB 3.0 and Toplink, which one should I choose? I prefer simplicity, and i think plain old java class is the best candidate. Any harm to use plain old java class for business layer? (FYI: View layer-ADF Faces & Model layer-ADF data model (Data Control & binding).

Get pdf file on how to understand ADF Model Layer. You may download the presentation from here:  download

This tutorial is similar with my previous posting. The only different is, page defintion file is not modified.

Download tutorial: TUTORIAL: Using Plain Java Class as business component for JSF page (Without modifying Page Definition File)