Conformance testing is coming in openEHR. It needs fleshing out (interested parties are welcome to contribute). I see the general shape of conformance testing as follows:
Content compliance - the system can receive, store and serve various test items of content; the served versions do not vary from the received versions - the system corerctly creates content due to a given series of calls to the vEHR API component (this API will be standardised in the near future) - the system corectly creates an EHR Extract in response to a give request. - the system correctly receives and integrates a test EHR Extract. - the system correctly responds to test queries System integration - the system correctly receives, converts and serves test messages (e.g. HL7v2) - etc for other formats, including CDA, PDF, text, etc - the system correctly connects to / integrates with IHE, HSSP and/or other recognised infrastructures. Services - the system correctly responds when each service function of the EHR and other services are exercised. Privacy - various tests to show that the privacy settings of a test user are respected during querying and other access methods Security - various tests to show that data integrity and signing are working Performace - various tests to indicate responds to single patient and populatin queries - volume tests Not all of these will necessarily be standardised by openEHR, but a sufficient number must be so that users of openEHR systems can have confidence in the correctness, safety, privacy and other aspects of systems. We would expect to group conformance tests into vrious profiles. - thomas beale -- Thomas Beale Chief Technology Officer Ocean Informatics
