search

I-TECH-UW / laboratory-workflows-ig

FHIR Implementation Guide for communication between an Electronic Medical Record (EMR) and a Lab Information System (LIS) using the OpenHIE (https://ohie.org/framework/) Architecture
https://i-tech-uw.github.io/laboratory-workflows-ig
Other
1 stars 3 forks source link

Create example FHIR resources #8 #12

Closed mozzy11 closed 3 years ago

mozzy11 commented 3 years ago

cc @pmanko

mozzy11 commented 3 years ago

hi @pmanko i can see the build fails because of
Publishing Content Failed: Unable to connect to terminology server. Error = Error fetching the server's capability statement: connect timed out (00:49.0079) The terminology server at http://tx.fhir.org is down

When you look at the build , SUSHI succesfully compiled all my changes and i can run this succesfully locally

I ran the CI build on the main repository without my changes and it still failed

mozzy11 commented 3 years ago

here is a screenshot of the IG running locally with the example resources i added image

and published on my repository here https://mozzy11.github.io/IG-PUBLISHER/artifacts.html

mozzy11 commented 3 years ago

hello @pmanko , The terminology server at http://tx.fhir.org is now up. i have re-run the jobs and it has passed. the ci build only fails at the deploy step since it can only acces the github_token when the PR is merged

mozzy11 commented 3 years ago

hey @pmanko , any comment on this. want to pick up another issue

pmanko commented 3 years ago

@mozzy11 sounds good - the github actions PR limitation is always a bit annoying -_-

pmanko commented 3 years ago

If you push your branch this repo, I can run the action on your branch manually - and possibly the tests won't fail?

pmanko commented 3 years ago

so PRs would always be from a I-TECH-UW/emr-lis-ig branch to main.

mozzy11 commented 3 years ago

the only problem ,is that if i push my PR to a branch , the Ig publisher would still update the gh-pages branch hence update the IG