Samenwerking voor de ontwikkeling van het elektronisch medisch voorschrift

Recip-e: Persbericht

Feitelijke vereniging Recip-e (april 2009)

Recip-e vzw opgericht: Persbericht 29 januari 2010
 

Collaboration pour le développement de la prescription médicale électronique

Recip-e: Communication de presse:

Association de fait: Recip-e (avril 2009)

Recip-e asbl: communiqué de presse 29 janvier 2010

Changelog:  Improvement of the error messages.

Prescriber module

Executor module
 

Changelog:  Improvement of the error messages.

Prescriber module

Executor module

Executor module

Executor module

• Recip-e Integration specification V 1. 9 0

   

  Prescriber module

  Executor module

• Recip-e Integration specification V 1. 9 0

   

  Prescriber module

  Executor module

• Changes versus V0.4.0 :
  • Minor Bug fixing (error management, etc)
  • MyCarenet (Executor module only), more information can be found in the integration specifications
    
    "*) The insurability orchestartion functionality is for the moment only available on the integration platform of eHealth (For development only). You will receive new configuration update instruction when the insurability orchestration functionality is available on PreProd platform.
    *) The direct connection is now available on the PreProd platform. "
     
• Recip-e Integration specification V 1. 8 0

   

  Prescriber module

  Executor module

• Changes versus V0.4.0 :
  • Minor Bug fixing (error management, etc)
  • MyCarenet (Executor module only), more information can be found in the integration specifications
    
    "*) The insurability orchestartion functionality is for the moment only available on the integration platform of eHealth (For development only). You will receive new configuration update instruction when the insurability orchestration functionality is available on PreProd platform.
    *) The direct connection is now available on the PreProd platform. "
     
• Recip-e Integration specification V 1. 8 0
   

  Prescriber module

  Executor module

• Changes compared to V0.3 :
  • Version connected to PreProd Environment (Internal Pilot)
  • New E-Health test certificates included
  • Bug Fixed :
    o Login with EID for which name contains specific characters
    o Decryption of prescription created with certificate no-longer valid

  Prescriber module

  Executor module

• Changes compared to V0.3 :
  • Version connected to PreProd Environment (Internal Pilot)
  • New E-Health test certificates included
  • Bug Fixed :
    o Login with EID for which name contains specific characters
    o Decryption of prescription created with certificate no-longer valid

Prescriber module

Executor module

• Main changes  (Recip-e Integration Specification V 1.7 0:
  • Fallback session enabled (without EID)
  • Certificate Management simplified. Certificates are configured with following parameters :
    # The keypair of the system/application
    KEYSTORE_FILE=%CONF%/p12/NIHII-PHARMACY=66666219_20101019-122059.p12
    # The password of previous keypair
    KEYSTORE_PASSWORD=pharmacy.
    # The folder where should be stored the fallback keypairs (personal certificates)
    KEYSTORE_AUTH_P12_FOLDER=%CONF%/p12

Prescriber module

Executor module

• Main changes  (Recip-e Integration Specification V 1.7 0:
  • Fallback session enabled (without EID)
  • Certificate Management simplified. Certificates are configured with following parameters :
    # The keypair of the system/application
    KEYSTORE_FILE=%CONF%/p12/NIHII-PHARMACY=66666219_20101019-122059.p12
    # The password of previous keypair
    KEYSTORE_PASSWORD=pharmacy.
    # The folder where should be stored the fallback keypairs (personal certificates)
    KEYSTORE_AUTH_P12_FOLDER=%CONF%/p12

  Prescriber module

  Executor module

28/10/2010  Changes versus V0.2.0 :

• Kmehr schema is upgraded to version 20100901. ("ns1" prefix is not required anymore)

• Security enabled : the EID and the Pin code are requested on CreateSession().

  • Pharmacy : EID can be the one of anybody.

  • Prescriber : EID must belong to a valid prescriber. Contact us to link a test NIHII id to your EID.

• Application requires a system certificate to communicate with the server :

  • Pharmacy : system certificate is linked to the pharmacy (NIHII-PHARMACY). Test certificates are included in the SDK.

  • Prescriber : system certificate is linked to the responsible person of the software. A test certificate is included in the SDK, Contact us to get additional test certificate.

• Personal certificates are required for FallbackSession and must be added to the application keystore. Follow this procedure to get a personal certificate :

1. Use the ETEE requestor tool fase 1 to create an ehcsr. (http://wwwacc.ehealth.fgov.be/JWS/ETEE/etee-requestor_nl.jnlp)
   => Please fill in the correct contact information (personal email and group email).

2. Send an e-mail to acceptance-certificates@ehealth.fgov.be
   This e-mail must contain the generated ehcsr in step 1 and also the additional NIHII number needed for searching the ETK.

3. You will recieve an e-mail, using the contact information in step 1 , from eHealth (AccessCoordination) with in this e-mail the public key and root CA.        

4. Use the ETEE requestor tool fase 2 to generate and register the ETK's.
   Note : the tool “keystore explorer” can be used to maintain the keystore and define the passwords of each private key.

• Bug fixing :

  • NullPointerException on first hasValidSession() invokation

  • XSD loading issue when path contains spaces

  • Modules behind proxy configuration

• Sample : new Features :

  • Command line tools can run with a session already open previously (see option -Dsession)

  • GUI tools improved : Copy/Paste of RID

Prescriber module

Executor module

Contact Point for technical questions : Thibaut.henry@accenture.com

28/10/2010  Changes versus V0.2.0 :

• Kmehr schema is upgraded to version 20100901. ("ns1" prefix is not required anymore)

• Security enabled : the EID and the Pin code are requested on CreateSession().

  • Pharmacy : EID can be the one of anybody.

  • Prescriber : EID must belong to a valid prescriber. Contact us to link a test NIHII id to your EID.

• Application requires a system certificate to communicate with the server :

  • Pharmacy : system certificate is linked to the pharmacy (NIHII-PHARMACY). Test certificates are included in the SDK.

  • Prescriber : system certificate is linked to the responsible person of the software. A test certificate is included in the SDK, Contact us to get additional test certificate.

• Personal certificates are required for FallbackSession and must be added to the application keystore. Follow this procedure to get a personal certificate :

1. Use the ETEE requestor tool fase 1 to create an ehcsr. (http://wwwacc.ehealth.fgov.be/JWS/ETEE/etee-requestor_nl.jnlp)
   => Please fill in the correct contact information (personal email and group email).

2. Send an e-mail to acceptance-certificates@ehealth.fgov.be
   This e-mail must contain the generated ehcsr in step 1 and also the additional NIHII number needed for searching the ETK.

3. You will recieve an e-mail, using the contact information in step 1 , from eHealth (AccessCoordination) with in this e-mail the public key and root CA.        

4. Use the ETEE requestor tool fase 2 to generate and register the ETK's.
   Note : the tool “keystore explorer” can be used to maintain the keystore and define the passwords of each private key.

• Bug fixing :

  • NullPointerException on first hasValidSession() invokation

  • XSD loading issue when path contains spaces

  • Modules behind proxy configuration

• Sample : new Features :

  • Command line tools can run with a session already open previously (see option -Dsession)

  • GUI tools improved : Copy/Paste of RID

Prescriber module

Executor module

Contact Point for technical questions : Thibaut.henry@accenture.com

28/09/2010: Recip-e Integration Specification V 0.2

"Release note":
Module V0.2 : Main changes compared to V0.1 :

- Version connected to Recip-e central system.

- E-Health security is disabled (no eid required for authentication, test certificate
included in the module).

- New API(s) for session Management: createFallbackSession(), hasValidSession(), … (Refer
to spec for more information)
 

Prescriber module

Executor module

Version 0.3 will be published mid October including the full security management of e-Health (EID + Certificates), no change expected regarding the API. More information to be followed.
 

28/09/2010 Recip-e Integration Specification V 0.2

"Release note":
Module V0.2 : Main changes compared to V0.1 :

- Version connected to Recip-e central system.

- E-Health security is disabled (no eid required for authentication, test certificate
included in the module).

- New API(s) for session Management: createFallbackSession(), hasValidSession(), … (Refer
to spec for more information)
 

Prescriber module

Executor module

Version 0.3 will be published mid October including the full security management of e-Health (EID + Certificates), no change expected regarding the API. More information to be followed.
 

Dit (werk)document beschrijft een set van voorwaarden voor de interface tussen het softwarepaket van de voorschrijver (bv. huisarts) respectievelijk het softwarepakket van de uitvoerder (bvb. apotheek, kinesist, ambulant verpleegkundige) en het Recip-e systeem. Het identificeert gevalideerde ontwerpvereisten en beperkingen waaraan moet worden voldaan door de interfacingsoftware. Dit document is bestemd voor ontwikkelaars van de bedoelde toepassingen en voor de organisaties die verantwoordelijk zijn voor de testen van deze toepassingen.
De huidige versies van de integratiemodules zijn uitsluitend werkversies voor demonstratiedoeleinden en worden momenteel nog aan de voorziene testprocedures onderworpen. Deze versies kunnen bijgevolg nog worden aangepast. De definitieve versies van de integratiemodules zullen te gepasten tijde met vermelding van hun gevalideerde status worden gepubliceerd.
Het eHealth-platform en de vzw Recip-e kunnen in geen geval aansprakelijk worden gesteld voor elke vorm van schade, direct of indirect, secundair of bijkomstig, materieel of immaterieel, veroorzaakt door de gebruiker of derden, voortkomend uit het gebruik van de werkversies of van de gevalideerde versies van de integratiemodules, of uit de onmogelijkheid om deze te gebruiken.

De respectieve integratiemodules zelf vindt u hierna:
 

Ce document de travail décrit une série de conditions pour l’interface entre le logiciel des prescripteurs (p.ex. le généraliste), le logiciel des exécuteurs (p.ex. le pharmacien, le kinesithérapeute ou l'infirmier) et le système Recip-e. Il identifie les exigences et contraintes de conception validées auxquelles le logiciel d’interfaçage doit satisfaire. Ce document est destiné aux développeurs des applications visées et aux organisations responsables de tester ces applications. Les versions actuelles des modules d’intégration ne sont que des versions de travail à titre de démonstration qui font, à l’heure actuelle, l’objet des procédures de test. Ces versions peuvent donc encore être adaptées. Les versions définitives des modules d’intégration seront publiées en temps utile, avec mention de leur statut validé.
La plate-forme eHealth et l’asbl Recip-e ne peuvent, en aucun cas, être tenues pour responsables de tout dommage, direct ou indirect, secondaire ou accessoire, matériel ou moral, causé par l’utilisateur ou par des tiers, découlant de l’utilisation des versions de travail ou des versions validées des modules d’intégration ou de l’impossibilité d'utiliser celles-ci.

Vous trouvez les modules d'intégration respectifs ci-après: