Versions Compared

Old Version 3

changes.mady.by.user michele.foucart

Saved on

compared with

New Version 4

changes.mady.by.user michele.foucart

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Proposed change proposal process

Image RemovedImage Added

  1. The requester of the change fills the template " Change proposal " template with the details of the change and submit the change proposal
    1. Anyone can send a CP to eDSI Solution Provider. This is typically done by directly updating the repository if you have access; otherwise send it an email to the
    eHDSI
    1. functional mailbox (SANTE-EHEALTH-DSI@ec.europa.eu).
    2. Anyone can send a CP to eDSI Solution Provider functional mailbox using the change proposal template

  2. Unrealistic or CPs not in scope of eHealth DSI can be blocked by the DSI Solution Provider (For example "use dropbox")

  3. The new CPs are considered by the eHDSI solution provider (EC) who analizes the CP and consults the OpenNCP Community
    1. If the proposed change
    .
    1. During this process, the solution provider can eventually ask further details, ask questions to the requester.
    2. The eHDSI solution provider also consults the OpenNCP Steering Committee who provide advise.concerns a software bug for instance, it will follow the usual process for software bugs (Jira)

    3. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-eHealthDSI-xxx-00.doc and placed in Assigned. If CP is rejected it is moved to Rejected and submitter is informed of explanation for rejection. Likely reasons for rejection are: duplicate, merged, withdrawn or not enough information to understand the request. Rejected CPs can be resubmitted with more information for reconsideration

  4. eHDSI SP works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc. When CP is ready, latest version of CP is moved to Completed diretory and old versions are moved to old_versions

  5. DSI Solution Provider:

    1. makes directly decision in case of minor impact to eHealth DSI and the decision will be given for information to eHOMB. eHOMB can take the decision into discussion if necessary

    2. DSI Solution Provider declines CP and the decision will be given for information to eHOMB. eHOMB can take the decision into discussion if necessary.

    3. If CP has major impact DSI Solution Provider will make a proposal to eHOMB who will make the decision. Operational Management Board can consult Member State Expert Group according to the Governance Model. Any member of the eHOMB can also raise the decision to eHealth Network.

  6. Once approved by eHOMB or eHealth Network the specification becomes official eHealth DSI specification

...