Hi All,

Be sure to include certification boundaries, e.g., certify records 
available in a single facility. Records may be resident in multiple 
remote facilities with the Providers attempting to deal quickly with the 
Patient in their facility, e.g., traveling salesman (has a known homebase).

If the remote records are not accessible for some reason, e.g., the 
latest security issue, then the local Providers may be able to certify 
the records (incoming/outgoing) at that facility and proceed. 
Reconciling distributed records can be treated as a separate issue. The 
current Patient/Provider requirements may be superior.

These type certification issues are spread between the Provider and the 
IT fields, the IT field flush with examples. What is important here is 
whether the Providers can live with certification of locally available 
records perhaps with the knowledge that others exists but are currently 
unavailable. Some decision process is needed.

If not, then I would appreciate knowing what issues need to be resolved. 
If the Patient can wait and the occupied resources could be put to no 
better use, then let the Patient wait. However, that doesn't seem to be 
the 'usual' situation.

-Thomas Clark




Thomas Beale wrote:

> Patrick Lefebvre wrote:
>
>> Hi all,
>>
>> About certification mechanisms... a few remarks.
>>
>> (1) openEHR (eventually CEN) has to publish a list of "standard 
>> tests". I think of conformant messages in different syntaxes (XML, 
>> Corba, etc). These messages may be part of the openEHR &/or EHRcom 
>> specification. 
>
>
> agree
>
>> (1bis) Anyone could do so. People will adopt the good work ;-)) 
>
>
> agree
>
>> (2) National organisations, Universities, CEN, openEHR, other... 
>> independent or not, profit and non-profit organisations may 
>> certificate "openEHR compliant". Compliant with what ? Only the 
>> public, published specs should be a serious test. 
>
>
> correct. But any certification has to be managed by openEHR - other 
> there is no point of trust for the whole process.
>
>> (2bis) As for benchmarks, anyone should be able to verify that the 
>> certification results were serious. So anyone has to get the tests. 
>
>
> well, they're needed anyway, for any vendor or developer who wants to 
> get certified - obviously they need the "exam questions" to know how 
> to practice;-)
>
>> (3) People (Hospitals, Health Care Organisations, etc ) will pay for 
>> a product, but will not accept paying an undefinite fee. Product may 
>> be "certified by Veritas" or "Certified by TNO": the stamp value 
>> is/will be the certifier's reputation. 
>
>
> no doubt. Clearly openEHR has to make sure these certification 
> processes are not uneconomic for those getting certified. On the other 
> hand, commercial vendors should expect to pay something - openEHR 
> saves them millions by giving away free specifications...
>
>> (4) Such schemes are widely in use in Quality Insurance (ISO 9000 for 
>> example). The test is published and well-known; The tester/certifier 
>> is independent from the vendor/buyer; 
>
>
> yep.
>
> - thomas
>
>
> -
> If you have any questions about using this list,
> please send a message to d.lloyd at openehr.org
>



-
If you have any questions about using this list,
please send a message to d.lloyd at openehr.org

Reply via email to