Requirement Constraints

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Tuesday, 11 December 2012

EMR Appointment Features

Posted on 09:43 by Unknown

Let me list the most common features in the Appointment module and their priority using MoSCoW Method.

MoSCoW Method

M - MUST:
Describes a requirement that must be satisfied in the final solution for the solution to be considered a success.

S - SHOULD:
Represents a high-priority item that should be included in the solution if it is possible. This is often a critical requirement but one which can be satisfied in other ways if strictly necessary.

C - COULD:
Describes a requirement which is considered desirable but not necessary. This will be included if time and resources permit.

W - WON'T:
Represents a requirement that stakeholders have agreed will not be implemented in a given release, but may be considered for the future.

Feature 1

The system should provide the option of quickly registering a patient before booking an appointment without going full walk through of patient registration screen.

Use case

Patient is mandatory while booking an appointment. But for a new patient want to book appointment, then user should be able to create the patient in the system with the minimal information quickly and then use for the appointment booking.

MoSCoW

Must


Feature 2

The system should provide the option to view appointments as daily view, Weekly view and Monthly view

Use case

Practice often want to see how many appointments for a week by provider

MoSCoW

Must


Feature 3

The system should provide the option to schedule appointment for people or resource

Use case

Schedule Providers, Nurses, PAs and Schedule Resources – rooms, equipment, etc.

MoSCoW

Must


 

Feature 4

Audit Trail for each Appointment.

Use case

Often user will make more noise if someone modify or cancelled the existing appointments.
Each appointment should be under the audit trail. The audit information should show the following information

  1. Who and When the appointment is created.
  2. Who and When the appointment is modified and what they have modified (old value and new value)
  3. Who and when and why the appointment is deleted.
  4. Who and When and why the appointment is cancelled.

MoSCoW

Must

 

Feature 5

Report. The solution should provide the following on the Appointment Report Module

  1. Print Appointment Lists by day by each resource or all resource.
  2. Print Cancellation Summary by Week or by Month.
  3. Print No Show Summary by Week or By Month
  4. Print Super bill of the practice for the appointment by day or by week.

Use case

Use case is quite self-explanatory.

MoSCoW

Must

 

Feature 6

The Solution should allow appointments to be scheduled in various increments i.e., 15, 30 or 45 minutes, based on reason of visit.

Use case

Even though resource default slot time interval can be fixed, but for some appointment type, doctor may need more time apart from the default interval. Usually it will multiple of N times of default Time interval. Say for example, resource default time interval is 15 min, but at the time of appointment booking for appointment reason, the resource may need 30 min. So system should have the option extend the end time at the appointment level.

MoSCoW

Must

 

Feature 7

The Solution should notify the booking staff that patient has missed previous appointments.

Use case

In some of the practice, as a procedure, they will not allow further appointments for the patient if there are too many no shows in the past. If there are too many no shows, then it will be revenue loss for the doctor.

By showing this alert, user can take a call to avoid appointment booking or they can charge small amount on the patient for the previous missed appointments.

MoSCoW

Should



Feature 8

The Solution should have the ability to display all past and future appointments by a patient in chronological order.

Use case

This will help the users to cancel or analyze about the patient appointments.

MoSCoW

Should


Feature 9

Mark Appointments as Cancelled or No-Show. Very importantly, system should capture the reason when cancelling the appointment

Use case

This will help the user to cancel the appointment upon patient request.

MoSCoW

Should



Feature 10

Mark Appointments as deleted due to data entry error. Very Importantly, system should capture the reason when deleting the appointment and also it should be soft delete.

Use case

This will help the user to delete the appointment due to data entry error.

MoSCoW

Should

 

Feature 11

Allow overbooking (waiting list) for a given slot according resource preferences

Use case

This will help to user to create the appointment as waiting list for a particular slot according to resource preference(allow 1 or 2 or 3 waiting list for me). This way resource can utilize the time slot if someone is no Show.

MoSCoW

Should




Feature 12

Automatically updates pending appointments based on changes made to patient status (deceased or deactivated).

Use case

Use case is quite self-explanatory. On action, the system should inform the user it is going to move all the appointments to cancelled status with automated cancelled reason.

MoSCoW

Should



Feature 13

Block Times for Non-patient Activities.(i.e. lunch, Meetings, etc.). Should support recurrence pattern by Daily, Weekly, Monthly and yearly.

Use case

Use case is quite self-explanatory.

MoSCoW

Should



Feature 14

User Defined Colors for Coding Appointments Status. The solution should provide this setting by practice, can be overridden by resource and can be overridden by appointment if necessary.

Use case

Use case is quite self-explanatory.

MoSCoW

Should



Feature 15

Cut and Paste Appointments.

Use case

The Cut and Paste features of the Scheduler allow you to move selected appointment(s) to different time slots and/or schedules.

MoSCoW

Should





Feature 16

Duplicate Appointment Alert. When scheduling an appointment for a patient, system should alert the user if the particular patient already have an appointment schedule for the same date , for the same resource or for the different resource.

Use case

Use case is quite self-explanatory.

MoSCoW

Should



Feature 17

Move an appointment from one provider to another provider.

Use case

This feature is can be achieved if Cut and Past appointments is available (Feature No 16)

MoSCoW

Should

 

Feature 18

Reschedule an appointment without deleting or cancelling the appointment.

Use case

This feature is can be achieved if Cut and Past appointments is available (Feature No 16)

MoSCoW

Should


Feature 19

Appointment Remainder Service via email . The email reminders are automatically set to be sent out one week prior to a scheduled appt, and then also one day prior.

Use case

Use case is quite self-explanatory.

MoSCoW

Should

 

Feature 20

User Defined Colors for Coding Appointments type or reason. The solution should provide this setting by practice, can be overridden by resource and can be overridden by appointment if necessary.

Use case

Use case is quite self-explanatory.

MoSCoW

Should

 

Feature 21

Move an appointment in a series to a different service provider or Move an entire series of appointments to a different service provider

Use case

This will help the user to switch appointment resource if the particular resource moved out of the practice.

MoSCoW

Could




Feature 22

Block all the resource scheduler in the practice for the Holidays. This is similar to Feature 14, but there should be way to do the same action for all the available resource in the practice.

Use case

Use case is quite self-explanatory.

MoSCoW

Could



Feature 23

The system should provide the option creating appointments for non-providers such as Nurses, Lab, X-Ray, etc

Use case

Use case is quite self-explanatory.

MoSCoW

Could

 

Feature 24

Patients With Upcoming Appointments... When scheduling a patient, the system should popup if patient has upcoming appointments if any. Just count can be shown, on clicking of the count, appointment list details can be shown.

Use case

Use case is quite self-explanatory.

MoSCoW

Could



Feature 25

Generates patient instructions when booking particular appointments which can be printed as part of the appointment notification for the patient.

Use case

This will help particularly for the Test Visit. There might be some instructions for the patient be prepared before taking any test. http://labtestsonline.org/understanding/features/test-prep/.

Normally each practice will maintain the test instruction for some lab test. That will be given to the patient at the time of check out or at the appointment booking.

MoSCoW

Could



Feature 26

Change / cancel one appointment in a series without changing / cancelling the others.

Use case

This will help the user to change or cancel one appointment in a series (Created using Feature 4) without touching the other appointments belong in the same series. For example, for the post surgery follow up visit, patient may want to cancel one of the appointment due to unavailability.

MoSCoW

Could



Feature 27

Ability to book a series of appointments based on a care plan.e.g. Monthly appointments for pregnancy checks. e.g. Quarterly appointments for Diabetic patients.To do this, Solution should have the ability of searching free slot in the future for the given provider, preferred start and end time, etc..

Use case

This will help the user to book series of appointments in one click, instead of going each date and each slot and again and again select the same patient.  Additionally, the user can give a name for the series of the appointment created, so then for any future reference, they can pull all the appointments by giving the name of the series.

MoSCoW

Could



Feature 28

The Solution should have the ability Schedule Appointments with Single or Multiple Resources. (e.g. exam rooms, X-Ray machine, etc.)

Use case

This will help the patient to complete all type of visits in the same day. Here is an example;

Doctor order an X-Ray for the patient which can be taken within the practice itself.

So here there are two appointments; one with the test technician who will handle the Lab and after the X-Ray has been taken , the doctor has to review and Change the Notes.

So if the solution has the feature of booking appointment for multiple resource consecutively, then it will help the patient to meet the doctor on the same date after Lab part is over.

MoSCoW

Could

Read More
Posted in EMR Appointment Features | No comments

Monday, 26 November 2012

Spring Security hello world example

Posted on 19:23 by Unknown

Use Spring security to provide a simple login authentication form to secure URL access in web application.

Thanks to mkyong. This tutorial is based on his tutorial

Spring Security allows developer to integrate security features with J2EE web application easily, it highjacks incoming HTTP request via servlet filters, and implements “user defined” security checking.

In this tutorial, we show you how to integrate Spring Security 3.0 with Spring MVC web application to secure URL access. After implemented Spring security, to view the content of the page, users need to key in correct “username” and “password”

Technologies used :

    • Spring 3.0.5.RELEASE
    • Spring Security 3.0.5.RELEASE
    • Eclipse Indigo
    • JDK 1.6
    • Maven 3

 

      Step : 1 

      If you are new java and Maven, then first setup environment in your local document. This document will help you to set up Java, Maven and Tomcat.

      Step : 2

      In the Eclipse IDE, Select File –> New –> Other –> Maven Project as shown here.

      clip_image002

      In the next screen, Verify that the Create a simple project checkbox is disabled and click Next.

      clip_image002[4]

      In the next screen, Enter maven-archetype-webapp as a filter, select maven-archetype-webapp in the artifact list and click Next

      clip_image002[6]

      In the next screen, enter the values as shown and Click Finish

      clip_image002[8]

      After finish, the following project will be created with the folders as shown.

      clip_image002[1]

      Step : 3

      Let us create our java folder where we will create all required java classes here. Goto the Project SpringDemomvc->Src->Main and Right click and say  new folder. 
      Enter the new folder name as   "Java".
      Now let include this folder into Project build path.Follow the steps

      1. Select springdemomvc in the Navigator.
      2. Right Click and Select Properties
      3. Select Java Build Path in the Left hand Tree.
      4. Go to Source Tab
      5. Select "Add Folder" in the right hand side.
      6. Select Java Folder and click ok.
      7. Now select Edit and enter "**/*.java" in inclusion pattern in the top.


        image[23]

      Step : 4

      POM File changes. Let us do the following changes in the POM.XML File

      1. By default, Maven 3 will use the JDK 1.4 to compile the source of your project, which is rather old and obsolete. Fortunately, Maven comes with a Maven Compiler Plugin, which enable Maven to compile the project source with a particular JDK version.

      2. Spring Security Dependencies: To use Spring security 3.0, you need “spring-security-core.jar“, “spring-security-web.jar” and “spring-security-config.jar“.    

      Spring libraries are available in Maven central repository. Let us add this into POM.XML File as follows (You can remove all the content and copy from here and paste it)

      <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
      <modelVersion>4.0.0</modelVersion>
      <groupId>springdemomvc</groupId>
      <artifactId>springdemomvc</artifactId>
      <packaging>war</packaging>
      <version>0.0.1-SNAPSHOT</version>
      <name>springdemomvc Maven Webapp</name>
      <url>http://maven.apache.org</url>

      <properties>
      <spring.version>3.0.5.RELEASE</spring.version>
      </properties>

      <dependencies>
      <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <scope>test</scope>
      </dependency>

      <!-- Spring 3 -->
      <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-core</artifactId>
      <version>${spring.version}</version>
      </dependency>

      <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-web</artifactId>
      <version>${spring.version}</version>
      </dependency>

      <dependency>
      <groupId>org.springframework</groupId>
      <artifactId>spring-webmvc</artifactId>
      <version>${spring.version}</version>
      </dependency>

      <!-- Spring Security -->
      <dependency>
      <groupId>org.springframework.security</groupId>
      <artifactId>spring-security-core</artifactId>
      <version>${spring.version}</version>
      </dependency>

      <dependency>
      <groupId>org.springframework.security</groupId>
      <artifactId>spring-security-web</artifactId>
      <version>${spring.version}</version>
      </dependency>

      <dependency>
      <groupId>org.springframework.security</groupId>
      <artifactId>spring-security-config</artifactId>
      <version>${spring.version}</version>
      </dependency>

      </dependencies>
      <build>
      <finalName>springdemo</finalName>
      <plugins>
      <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <version>2.3.1</version>
      <configuration>
      <source>1.6</source>
      <target>1.6</target>
      </configuration>
      </plugin>
      </plugins>
      </build>
      </project>




       


      Step : 5



      A simple Spring MVC to return a “hello.jsp” page, via URI “/welcome“. Later use Spring security to secure this URL access. Select java folder and Select new Class.  Give the package name as "com.example.common.controller" and class name as "HelloController". After clicking Finish, folders will be created and will look as follows

      image
      And paste the following code in the java file


      package com.example.common.controller;

      import org.springframework.stereotype.Controller;
      import org.springframework.ui.ModelMap;
      import org.springframework.web.bind.annotation.RequestMapping;
      import org.springframework.web.bind.annotation.RequestMethod;

      @Controller
      @RequestMapping("/welcome")
      public class HelloController {

      @RequestMapping(method = RequestMethod.GET)
      public String printWelcome(ModelMap model) {

      model.addAttribute("message", "Spring Security Hello World");
      return "hello";

      }

      }







      Step : 6



      Now let us create the JSP Page. Create a new folder called "Pages" under webapp\web-inf folder as shown here.

      image
      Now right click on pages folder and Select new jsp file and give the name as "hello.jsp". Replace the default content and paste the following



      <html>
      <body>
          <h1>Message : ${message}</h1>
      </body>
      </html>

      image



      Step : 7



      Right click on web-INF Folder and Select new file and Enter the file name as "mvc-dispatcher-servlet.xml"

      image
      Paste the following content


      <beans xmlns="http://www.springframework.org/schema/beans"
      xmlns:context="http://www.springframework.org/schema/context"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="
      http://www.springframework.org/schema/beans
      http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
      http://www.springframework.org/schema/context
      http://www.springframework.org/schema/context/spring-context-3.0.xsd"
      >

      <context:component-scan base-package="com.example.common.controller" />

      <bean
      class="org.springframework.web.servlet.view.InternalResourceViewResolver">
      <property name="prefix">
      <value>/WEB-INF/pages/</value>
      </property>
      <property name="suffix">
      <value>.jsp</value>
      </property>
      </bean>

      </beans>





      Step : 8



      Now let us add the spring security. Right click on web-INF Folder and Select new file and Enter the file name as "spring-security.xml"
      image
      Paste the following content



      <beans:beans xmlns="http://www.springframework.org/schema/security"
      xmlns:beans="http://www.springframework.org/schema/beans"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.springframework.org/schema/beans
      http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
      http://www.springframework.org/schema/security
      http://www.springframework.org/schema/security/spring-security-3.0.3.xsd"
      >

      <http auto-config="true">
      <intercept-url pattern="/welcome*" access="ROLE_USER" />
      </http>

      <authentication-manager>
      <authentication-provider>
      <user-service>
      <user name="mkyong" password="123456" authorities="ROLE_USER" />
      </user-service>
      </authentication-provider>
      </authentication-manager>

      </beans:beans>



      Step : 9



      To integrate Spring security with web application, just declare “DelegatingFilterProxy” as servlet filter to intercept incoming request.Open WEB.xml and replace with the following one.


      <web-app id="WebApp_ID" version="2.4"
      xmlns="http://java.sun.com/xml/ns/j2ee"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
      http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
      >

      <display-name>Spring MVC Application</display-name>

      <!-- Spring MVC -->
      <servlet>
      <servlet-name>mvc-dispatcher</servlet-name>
      <servlet-class>
      org.springframework.web.servlet.DispatcherServlet
      </servlet-class>
      <load-on-startup>1</load-on-startup>
      </servlet>
      <servlet-mapping>
      <servlet-name>mvc-dispatcher</servlet-name>
      <url-pattern>/</url-pattern>
      </servlet-mapping>

      <listener>
      <listener-class>
      org.springframework.web.context.ContextLoaderListener
      </listener-class>
      </listener>

      <context-param>
      <param-name>contextConfigLocation</param-name>
      <param-value>
      /WEB-INF/mvc-dispatcher-servlet.xml,
      /WEB-INF/spring-security.xml
      </param-value>
      </context-param>

      <!-- Spring Security -->
      <filter>
      <filter-name>springSecurityFilterChain</filter-name>
      <filter-class>
      org.springframework.web.filter.DelegatingFilterProxy
      </filter-class>
      </filter>

      <filter-mapping>
      <filter-name>springSecurityFilterChain</filter-name>
      <url-pattern>/*</url-pattern>
      </filter-mapping>

      </web-app>


      Step : 10
                   Now let us start the server and type the url “http://localhost:8080/springdemo/welcome”. Now spring will redirect to login page.

      Read More
      Posted in Spring Security | No comments

      Wednesday, 21 November 2012

      ZK Grid CSS

      Posted on 20:50 by Unknown

      image

      <zk>

      <style>
      .fgrid tr.z-row td.z-row-inner,tr.z-row,div.z-grid-body
      div.z-cell,div.z-grid { border: none; overflow: hidden; zoom: 1;
      background: white; border-top: none; border-left: none;
      border-right: none; border-bottom: none; }

      .fgrid .z-grid-odd .fgrid .z-row-inner,.fgrid .z-grid-odd
      .z-cell { background-color: #F7F7F7; border-bottom: 1px solid
      transparent; border-left: 1px solid transparent; border-top: 1px
      solid transparent; }

      .fgrid .z-grid-odd .fgrid.z-row-inner,.fgrid.z-grid-odd
      .z-cell,.fgrid.z-grid-odd { background: none repeat scroll 0 0
      transparent; }

      .fgrid tr.z-grid-odd td.z-row-inner,.fgrid tr.z-grid-odd
      .z-cell,.fgrid tr.z-grid-odd { background: white }

      .fgrid tr.z-row td.z-row-inner,.fgrid tr.z-row .z-cell {
      background: white; border-top: none; }


      </style>

      <window id="win" width="99%" height="auto">
      <label value="Grid without sclass " style="font-size :20px;" />
      <panel width="100%">
      <panelchildren>
      <separator />
      <grid hflex="min">
      <columns>
      <column hflex="min" align="right" />
      <column hflex="min" />
      <column hflex="min" align="right" />
      <column hflex="min" />
      <column hflex="min" align="right" />
      <column hflex="min" />
      <column hflex="min" align="right" />
      <column hflex="min" />
      <column hflex="min" align="right" />
      <column hflex="min" />
      </columns>
      <rows>
      <row>
      <label value="Salutation" />
      <textbox />
      <label value="Last Name" />
      <textbox />
      <label value="First Name" />
      <textbox />
      <label value="Middle Name" />
      <textbox />
      </row>
      <row>
      <label value="Suffix" />
      <textbox />
      <label value="Gender" />
      <textbox />
      <label value="DOB" />
      <textbox />
      <label value=" " />
      <label value=" " />
      <label value=" " />

      </row>
      <row>
      <label value="SSN" />
      <textbox />
      <label value="Marital Status" />
      <textbox />
      <label value="" />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <cell colspan="8">
      <separator bar="true" />
      </cell>
      </row>

      <row>
      <cell colspan="8" style="" align="left">
      <label value="Contact Details" />
      </cell>
      </row>


      <row>
      <label value="Address:" />
      <cell colspan="3">
      <textbox rows="1" hflex="1" />
      </cell>
      <label value="" />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <label value="" />
      <cell colspan="3">
      <textbox rows="1" hflex="1" />
      </cell>
      <label value="" />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <label value="City" />
      <textbox rows="1" hflex="1" />
      <label value="State" />
      <textbox />
      <label value="ZipCode " />
      <textbox />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <label value="Home Phone" />
      <textbox />
      <label value="Office Phone" />
      <span>
      <textbox width="100px" />
      <textbox width="30px" />
      </span>
      <label value="Mobile" />
      <textbox />
      <label value="Fax" />
      <textbox />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <label value="Email" />
      <cell colspan="3">
      <textbox rows="1" hflex="1" />
      </cell>
      </row>
      </rows>
      </grid>
      </panelchildren>
      </panel>
      </window>
      <window id="win1" width="99%" height="440px">
      <label value="Grid with sclass " style="font-size :20px;" />
      <panel width="100%">
      <panelchildren>
      <separator />
      <grid hflex="min" sclass="fgrid">
      <columns>
      <column hflex="min" align="right" />
      <column hflex="min" />
      <column hflex="min" align="right" />
      <column hflex="min" />
      <column hflex="min" align="right" />
      <column hflex="min" />
      <column hflex="min" align="right" />
      <column hflex="min" />
      <column hflex="min" align="right" />
      <column hflex="min" />
      </columns>
      <rows>
      <row>
      <label value="Salutation" />
      <textbox />
      <label value="Last Name" />
      <textbox />
      <label value="First Name" />
      <textbox />
      <label value="Middle Name" />
      <textbox />
      </row>
      <row>
      <label value="Suffix" />
      <textbox />
      <label value="Gender" />
      <textbox />
      <label value="DOB" />
      <textbox />
      <label value=" " />
      <label value=" " />
      <label value=" " />

      </row>
      <row>
      <label value="SSN" />
      <textbox />
      <label value="Marital Status" />
      <textbox />
      <label value="" />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <cell colspan="8">
      <separator bar="true" />
      </cell>
      </row>

      <row>
      <cell colspan="8" style="" align="left">
      <label value="Contact Details" />
      </cell>
      </row>


      <row>
      <label value="Address:" />
      <cell colspan="3">
      <textbox rows="1" hflex="1" />
      </cell>
      <label value="" />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <label value="" />
      <cell colspan="3">
      <textbox rows="1" hflex="1" />
      </cell>
      <label value="" />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <label value="City" />
      <textbox rows="1" hflex="1" />
      <label value="State" />
      <textbox />
      <label value="ZipCode " />
      <textbox />
      <label value=" " />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <label value="Home Phone" />
      <textbox />
      <label value="Office Phone" />
      <span>
      <textbox width="100px" />
      <textbox width="30px" />
      </span>
      <label value="Mobile" />
      <textbox />
      <label value="Fax" />
      <textbox />
      <label value=" " />
      <label value=" " />
      </row>

      <row>
      <label value="Email" />
      <cell colspan="3">
      <textbox rows="1" hflex="1" />
      </cell>
      </row>
      </rows>
      </grid>
      </panelchildren>
      </panel>
      </window>
      </zk>

      Read More
      Posted in ZK CSS | No comments
      Newer Posts Older Posts Home
      Subscribe to: Posts (Atom)

      Popular Posts

      • ZK Example for inline Editing with Add New and Delete
        I am quite impressed on this demo from ZK . But adding new record and delete existing record is missing as part of typical CRUD. So i thoug...
      • EDI 5010 Documentation 837 Professional - Loop 2010BB Payer Name
        2010BB Payer Name          In this loop, all the information will be taken from Insurance master screen. Take a look of our sample screen...
      • EDI 5010 Documentation–837 - BHT - Beginning of Hierarchical Transaction
        BHT – Beginning of Hierarchical Transaction Loop Seg ID Segment Name Format Length Ref# Req Value   BHT Beginning of Hier...
      • Hibernate Validator Example 2
        In this example, we will see some more validation constraints such as @email, @past, @length, etc. And also we will also define custom error...
      • ZK Passing Parameter between two files using MVVM–Part 1
        Overview This is the first series of articles about Passing parameter between two zul files using MVVM Design pattern .This article will fo...
      • MVVM Command annotation and Notify change example
        Here is an example, how to pass parameter on a zul through MVVM Command binding annotation. ZK URL http://books.zkoss.org/wiki/ZK%20Develo...
      • History of Present Illness
        HPI - One of the main component of Clinical History. What is an HPI ? The history of present illness (HPI) is a chronological description...
      • Patient Demographics
        Patient browse (search) is the key element for any EMR / PMS Software. In my past 15 years experience, i involved more than 5 times in desig...
      • ViewModel Class Java Annotation @Init, @NotifyChange, @Command
        In following sections we'll list all syntaxes that can be used in implementing a ViewModel and applying ZK bind annotation. The ZK binde...
      • Good Website Design Links
        Form Design Label Placement in Forms International Address Fields in Web Forms 40 Eye-Catching Registration Pages blog-comment-form-...

      Categories

      • Billing Process
      • C Workbook
      • C++ Workbook
      • Eclipse Tips
      • EDI 5010
      • EMR Appointment Features
      • EMR Labs Stuff
      • EMR PMS Links
      • EMR Use cases
      • EMR Vital Sign
      • Good Website Design
      • Hibernate Criteria Queries
      • Hibernate Introduction
      • Hibernate Introduction Setup
      • Hibernate Mapping
      • Hibernate POC
      • Hibernate Validator
      • Hibernate–Java Environment setup
      • HPI
      • Java
      • Maven
      • MU Certification
      • NPI
      • PQRS
      • Practice Management System
      • Spring Security
      • Tech Links
      • Today Tech Stuff
      • zk
      • ZK Hibernate
      • ZK 5 Databinding
      • ZK Application
      • ZK Calling Another ZUL
      • ZK CheckBox
      • ZK CreateComponents
      • ZK CSS
      • ZK extended Components
      • ZK Foreach
      • ZK Forum Posts
      • ZK Framework
      • ZK Hibernate Setup
      • ZK ID Space
      • ZK Include
      • ZK Installation
      • ZK iReport
      • ZK Layout
      • ZK Listitem Pagination
      • ZK Message Box
      • ZK MVC
      • ZK MVC Combox Box
      • ZK MVC CRUD Examples
      • ZK MVC Listbox
      • ZK MVVM
      • ZK MVVM Combo
      • ZK MVVM CRUD
      • ZK MVVM ListBox
      • ZK Spring
      • ZK TextBox

      Blog Archive

      • ►  2013 (105)
        • ►  December (3)
        • ►  September (7)
        • ►  August (13)
        • ►  July (1)
        • ►  June (11)
        • ►  May (3)
        • ►  April (14)
        • ►  March (19)
        • ►  February (21)
        • ►  January (13)
      • ▼  2012 (177)
        • ▼  December (1)
          • EMR Appointment Features
        • ►  November (13)
          • Spring Security hello world example
          • ZK Grid CSS
        • ►  October (19)
        • ►  September (24)
        • ►  August (26)
        • ►  July (6)
        • ►  June (37)
        • ►  May (30)
        • ►  April (16)
        • ►  March (1)
        • ►  January (4)
      • ►  2011 (5)
        • ►  December (1)
        • ►  November (1)
        • ►  July (1)
        • ►  June (1)
        • ►  April (1)
      • ►  2010 (1)
        • ►  September (1)
      Powered by Blogger.

      About Me

      Unknown
      View my complete profile