Changes between Version 3 and Version 4 of LEGACY - Northampton Recruitment into BRICCS


Ignore:
Timestamp:
03/14/13 14:52:25 (12 years ago)
Author:
Nick Holden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LEGACY - Northampton Recruitment into BRICCS

    v3 v4  
     1= BRICCS: Northampton recruitment =
     2
    13After much deliberation and discussion, there will be BRICCS recruitment in Northampton soon.
    24
    … …  
    2224
    2325
    24 Plan now:
     26== Plan now:  ==
    2527
    2628* Get Onyx working on the uhlbriccsext01 server, including test/training deployment, with manual patient entry
    27   * Add participant attributes for 'NHS number' and 'local site unique identifier' for NGH patient ID.
     29  * Add participant attribute for 'local site unique identifier' for NGH patient ID.
    2830
    2931* Establish VPN or tunnel access between client machines and server - Neil Baker and Steve Wenlock working on this
    … …  
    4345* Begin recruiting
    4446
     47== Update ==
    4548
     49Steve Wenlock and Neil Baker have discussed this. VPN is 'overkill' for the level of complexity involved. Steve suggests a more straightforward approach of ensuring the server runs over SSL and then opening the necessary port in the UHL firewall and forwarding it explicitly to the server - with a DNS entry being made in N3 to route the connection.
     50
     51OBiBa's wiki does describe the deployment of Onyx over SSL: http://wiki.obiba.org/display/ONYX/SSL+Deployment
     52
     53Tomcat over SSL uses port 8443. I've installed a self-signed test certificate on the server, for testing purposes, and that works satisfactorily.
     54
     55In Onyx config, make the following changes: WEB-INF/config/messages_en.properties needs a line to add "pat_local_id= Local patient ID" and WEB-INF/config/participant-attributes.xml needs a stanza to define pat_local_id as assignable at enrollment, editable, but not mandatory.