Release schedule:
2.0.0: March 25th
1º Sprint: 28Jan > 8 Fev (2 weeks)
2º Sprint: 11Fev > 22Fev (2 weeks)
3º Sprint: 29Fev > 8Mar (2 weeks)
4º Sprint: 11Mar > 22Mar (2 weeks) (<- both weeks, or perhaps just the last week could be the code freeze?)
Release date: 25March > OpenNCP 2.0.0
Themes for the sprints
- PAC (Patient Access) [OpenNCP 2.0.0]
- All terminology (translations/transcoding) should be at the NCP-A (LTR component) side;
- Discover language: What and how will we provide the list of available languages?
- a. static page in portal; b. central services asynchronous synchronization (current process - like countries Patient search Identification method); c. real time central service request (CTS2 transaction);
- Articulate with CareCom (Annika): How can TSAM sync with aimed languages (more that one > current implementation sync only one language)
- HCER (Health Care Encounter Report) [OpenNCP 2.0.0]
- Patient Summary with an alternative format, uses XCA/XDR.
- NCP: workflow communication Country-B (produces request) Country-A (acknowledge response)
- [Out of OpenNCP scope] NI-A: will use the information accordingly the country strategy;
- MRO (Medication Related Overview) [OpenNCP 2.1.0]
- could possibly be linked with the Patient Access?
- XCF implementation for OpenNCP [OpenNCP 2.2.0]
Deferred implementation items (need more information before scheduling)
- Updates to tsam-synchronizer (CTS2 compliant) in light of the new Terminology Server
- implementation specification still to be finalized.
- [Out of OpenNCP scope] Implement the NEW Terminology Server (replacing the current server - central service)
- ESS (the jury is apparently still out on the issue of PACE licensing)