clearhealth 1.0 (CHMED API branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News clearhealth 1.0 (CHMED API branch)
# 1  
Old 07-20-2008
clearhealth 1.0 (CHMED API branch)

ImageClearHealth is a fully comprehensive practice management system and EMR. It takes DNA from the FreeMED and OpenEMR projects, and is based on the Smarty templatingengine. It includes support for medications, SOAPdata entry, clinical reporting, e-prescribing, and labs. Feature for feature, it can compete with proprietary systems like Nextgen and GE Centricity. It includes support for the iPhone and iPod touch (native application).Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Web Development

Face-api.js — JavaScript API for Face Recognition in the Browser with tensorflow.js

Ref: https://itnext.io/face-api-js-javascript-api-for-face-recognition-in-the-browser-with-tensorflow-js-bcc2a6c4cf07 (0 Replies)
Discussion started by: Neo
0 Replies

2. Shell Programming and Scripting

Need to run an API from a script and extract fields from output of API

Hi, I need to call an API (GetUsageDetails)from inside a shell script which takes an input argument acct_nbr. The output of API will be like : <usageAccum accumId="450" accumCaptn="PM_125" inclUnits="1410.00" inclUnitsUsed="744.00" shared="true" pooled="false" prorated="false"... (1 Reply)
Discussion started by: rkrish
1 Replies
Login or Register to Ask a Question
emulate_branch(3)					     Library Functions Manual						 emulate_branch(3)

Name
       emulate_branch, execute_branch - branch emulation

Syntax
       #include <signal.h>

       emulate_branch(scp, branch_instruction)
       struct sigcontext *scp;
       unsigned long branch_instruction;

       execute_branch(branch_instruction)
       unsigned long branch_instruction;

Description
       The  function  is  passed  a signal context structure and a branch instruction.	It emulates the branch based on the register values in the
       signal context structure.  It modifies the value of the program counter in the signal context  structure  (sc_pc)  to  the  target  of  the
       branch_instruction.   The program counter must initially be pointing at the branch and the register values must be those at the time of the
       branch.	If the branch is not taken the program counter is advanced to point to the instruction after the delay slot (sc_pc += 8).

       If the branch instruction is a `branch on coprocessor 2' or `branch on coprocessor 3' instruction, calls to  execute  the  branch  in  data
       space to determine if it is taken or not.

Return Values
       The  function returns a 0 if the branch was emulated successfully.  A non-zero value indicates the value passed as a branch instruction was
       not a branch instruction.

       The function returns non-zero on taken branches and zero on non-taken branches.

Restrictions
       Since is only intended to be used by it does not check its parameter to see if in fact it is a branch instruction.  It is really a stop gap
       in case a coprocessor is added without the kernel fully supporting it (which is unlikely).

See Also
       cacheflush(2), sigvec(2), signal(3)

								       RISC							 emulate_branch(3)