AMECO Group UHR Project Tracker

9 of 45

Stages doneRiyadh 6, Al Hamra 3, Al Hasa 0

—

Days on the longest open blockerNo open item has a start date

Open blockers

Days to the staging targetAll use cases, 30 September

RiyadhAl HamraAl Hasa|ONA → STG → PRD ONA = testing on SehaPassedBlocked by othersPendingNot started

Branch and use caseONASTGPRDDoneNext byBlocked onAction byOur part

RiyadhCHI 1088ONASTGPRD6 of 15 stages donePartly liveClinical Notes is the only one still in development.

ADT2 of 3Mid Oct—CloudtechMove to production at go liveWhyShow less

ONA passed and the staging endpoint has been working since 10 September. No Obeid email names a single ADT event code. The event list that used to sit here came from a different programme and was never said of Obeid, so it has been removed. One email to LEAN asking which ADT triggers Obeid has passed in staging closes the question.

Lab2 of 3Mid Oct—CloudtechMove to production at go liveWhyShow less

ONA passed, and lab is through staging. The endpoint on port 11620 had timed out since 10 September. The cause was the whitelist: once our address was added, the endpoint answered. Nothing on Riyadh is held up now — production at go live is what is left.

Radiology1 of 330 Sep—CloudtechSubmit to the staging endpointWhyShow less

Order and result both passed ONA on 14 September. Staging is next.

Medication1 of 330 Sep—CloudtechSubmit to the staging endpointWhyShow less

e-Prescribe and e-Dispense both passed ONA on 15 September.

Clinical Notes0 of 323 Sep—CloudtechFinish the build and test on SehaWhyShow less

The only Riyadh use case still in development. Seha testing is planned for 23 September.

Code mappingn/an/a—Delivered—Obeid Riyadh departmentsComplete mapping shared, ready for the next stepWhyShow less

The complete mapping is shared: all 4,349 hospital codes are mapped. 62% high confidence, ready to submit. 16% medium confidence and 23% low confidence, and almost all of the medium and low sit in Laboratory and Radiology. Those two can be lifted quickly if the hospital can supply a little more detail: for Lab, the analyte, specimen type, method, result type and unit of measure; for Radiology, the modality, body region, laterality and contrast. It can come either as an export from the LIS and RIS, or by adding the detail into the hospital descriptions themselves, whichever is easier for the teams. If the descriptions cannot be changed, what has been shared stands as the final mapping from our side and we proceed on that basis. Either way, we are ready to move to the next step.

See what would lift the medium and low codes

Needed firstSingle sign-onconfirmed by LEANRegistriesall three

Al HamraCHI 1114ONASTGPRD3 of 15 stages doneADT and lab open, rest notLEAN opens the portal one use case at a time. ADT and lab are open here.

ADT2 of 3Mid Oct—CloudtechMove to production at go liveWhyShow less

Passed ONA, and the staging endpoint on port 2187 is shared and running. Finished business: the OID validation failure of 30 August happened here, on this branch's own ADT staging test, and ADT has passed since. The fault was the middle arc, not the facility number. The message went out with 2.16.840.1.113883.3.3731.5.1.10000300170444 against the correct 2.16.840.1.113883.3.3731.6.440.10000300170444. Same root, same facility tail, wrong branch in the middle. It never touched lab, radiology or medication. One loose end: the same acknowledgement also failed terminology validation on an invalid coded field, WARD G. ADT passing suggests it was corrected, but nothing in email confirms it, so it is worth checking it was fixed rather than worked around.

Lab1 of 330 Sep—CloudtechSubmit to the staging endpointWhyShow less

LEAN has opened this use case for the branch. Order and result were both tested on the Seha portal on 19 September. Nothing had to be built — the Riyadh build carried across without change. Staging is next, and the endpoint for it still has to come from LEAN.

Radiology0 of 3Awaiting LEANLEANDr. Pathan, with LEANReady, build carried across from RiyadhWhyShow less

Built and carried across from Riyadh. Waiting for LEAN to open the use case, the same as medication and clinical notes.

See the portal blocker

Medication0 of 3Awaiting LEANLEANDr. Pathan, with LEANReady, build carried across from RiyadhWhyShow less

Built and carried across from Riyadh. Waiting for LEAN to open the use case, the same as radiology and clinical notes.

See the portal blocker

Clinical Notes0 of 3After 23 SepLEANDr. Pathan, with LEANFollows the Riyadh buildWhyShow less

Two things have to happen before this one can be tested: the Riyadh build has to pass ONA on 23 September, and LEAN has to open the use case for this branch, the same as radiology and medication.

See the portal blocker

Code mappingn/an/a—Starts 24 Sep—Al Hamra departmentsOne pass covers Al Hamra and Al HasaWhyShow less

Begins once the Riyadh mapping review closes on 24 September. One pass covers both Al Hamra and Al Hasa, carrying the code work across from the Riyadh catalogue, so this is review work rather than a fresh start.

Needed firstSingle sign-ondone on productionRegistriesall three

Al HasaCHI 1144ONASTGPRD0 of 15 stages donePortal not openNothing on this branch is waiting on Cloudtech.

ADT0 of 325 SepLEANObeid, chasing LEANReady to test as soon as the portal opens and endpoints are sharedWhyShow less

Targeted at 25 September for ONA. That date holds only if LEAN opens the Seha portal for the branch first. The portal onboarding is delayed on LEAN's side, and Obeid is following it up. Once the portal opens and the endpoints are shared, Cloudtech is ready to test.

See the Seha portal blocker

Lab0 of 325 SepLEANObeid, chasing LEANReady to test as soon as the portal opens and endpoints are sharedWhyShow less

See the Seha portal blocker

Radiology0 of 325 SepLEANObeid, chasing LEANReady to test as soon as the portal opens and endpoints are sharedWhyShow less

See the Seha portal blocker

Medication0 of 325 SepLEANObeid, chasing LEANReady to test as soon as the portal opens and endpoints are sharedWhyShow less

See the Seha portal blocker

Clinical Notes0 of 325 SepLEANObeid, chasing LEANReady to test as soon as the portal opens and endpoints are sharedWhyShow less

See the Seha portal blocker

Code mappingn/an/a—Starts 24 Sep—Al Hasa departmentsSame pass as Al HamraWhyShow less

Covered by the same pass as Al Hamra, starting 24 September.

Needed firstSingle sign-ondone on production, LEAN confirmedRegistriesall threeServerAl Hasa is arranging it, to complete production single sign-onSeha portal onboardingdelayed on LEAN's side. Obeid is following it up

Who we are waiting on

Riyadh·Cloudtech waitingNot blockingObeid RiyadhExtra lab and radiology detail would lift the medium and low confidence codes. Action: Dr. Pathan and department headsFind out moreShow less

Extra lab and radiology detail would lift the medium and low confidence codes. Action: Dr. Pathan and department heads

This does not hold anything up. The complete mapping is shared and 62% came back high confidence, ready to submit. The remaining 16% medium and 23% low sit almost entirely in Laboratory and Radiology, and a little more detail from the hospital would lift most of them: for Lab, analyte, specimen type, method, result type and unit of measure; for Radiology, modality, body region, laterality and contrast. Either an export from the LIS and RIS, or the detail added into the hospital’s own descriptions, whichever is easier for the teams. If the descriptions cannot be changed, what has been shared stands as the final mapping and we proceed on that basis.

Back to the table

Al Hamra·Al Hamra and Cloudtech waitingOpenLEANLEAN opens the portal one use case at a time. ADT and lab are open; three still to request. Action: Dr. Pathan, requesting each use case from LEANFind out moreShow less

LEAN opens the portal one use case at a time. ADT and lab are open; three still to request. Action: Dr. Pathan, requesting each use case from LEAN

LEAN opens the Seha portal one use case at a time, with a dedicated endpoint for each. The ADT thread says so in its own opening line — the branch was declared ready to proceed to staging in the ADT use case, and got an endpoint for that use case alone. Lab was opened next and tested on Seha on 19 September. Radiology, medication and clinical notes are built and carried across from Riyadh, so there is nothing left to develop; they simply cannot be submitted until LEAN unlocks each one. The same request has to be made three more times. The 30 August OID failure is not the blocker: it happened on this branch's own ADT test, the arc has been corrected, and ADT has passed since.

Back to the table

Al Hasa·Obeid and Cloudtech waitingOpenLEANThe whole branch. Obeid is following up with LEAN on the Seha portal. Action: Obeid, following up with LEANFind out moreShow less

The whole branch. Obeid is following up with LEAN on the Seha portal. Action: Obeid, following up with LEAN

Portal access for the Al Hasa branch is not complete, so conformance testing cannot open at all. This is not a Cloudtech deliverable, and it is not a form the hospital has failed to send — it sits with LEAN, and Obeid is following it up. Until the portal opens and the endpoints are shared, none of the five use cases can be submitted. The build itself is ready. All five are targeted at 25 September, and that date holds only if the portal opens first.

Back to the table

Risk. Al Hasa cannot start until LEAN opens its Seha portal, and it has about two weeks between the staging close and production go live.

Timeline and email historyShow less

Dated

5 NovCHI UHR Phase 1 deadlineAll three
Mid OctProduction go liveAll three

Nobody has set a date for these

Date not setSeha portal opened by LEANAl Hasa
Date not setLEAN opens the remaining three use casesAl Hamra