mlhim-owners team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

On Mon, 2010-08-16 at 09:53 -0300, Diego Manhães Pinheiro wrote:
> Hi Tim!
> 
> 
> Last weekend I'm thinking about interface design issues to the OSHIP,
> when I remembered that you glance a implementation using the design
> guidance created by MSCUI. I found some information that you put on
> the OpenEHR web site forum discussion, mainly about license details,
> but didn't follow properly. So, How is going ? Is there any license
> agreement problem to implement the microsoft design guidance on a
> different platform such as YUI, JQuery or similar ? Is there a project
> which are developing these design guidances using
> other technologies instead of Silverlight and related Microsoft
> frameworks ? 
> I'm getting ahead on this topic because user interface creates a large
> impact on the web system. I reckon this topic should be included on
> the top list of the OSHIP requirements.
> 

Hi Diego,

You are correct.  This is important for everyone.  

The MSCUI is a collaborative work between the UK NHS and Microsoft.  A
great deal of research as well as Microsoft's experience went into this
effort. 

While we cannot re-publish the specifications.  I do have an email
confirmation that it is completely legal to implement the MSCUI in any
product, including open source products, without a fee. Reading the
legal documents and the confusion between the UK Crown Copyright and
Microsoft's morass is almost impossible. :-)
 
The concepts and consistency in this specification makes sense to me.
And AFAIK there is no other existing specification for user interfaces,
much less anything in healthcare.

We do not currently have people to work on this project but I do have
plans to implement these specifications, as you mentioned, using the YUI
tools. 

The information is here: http://www.mscui.net/Introduction/MSCUI.aspx

There is an NHS site http://www.cuisecure.nhs.uk/ that I know has the
PDFs of the actual specs.  But it requires a login.  I do not recall
right now how I got my login.  :-(  

Anyway, by the time we have a team to begin working on this library I
will acquire of the specs. 


Regards,
Tim

Attachment: signature.asc
Description: This is a digitally signed message part