You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we uploaded a cleaned-up message inventory to gitHub it triggered the build and got a new IG. It did include 4575 errors, but seemed all to be similar. So that is not the problem at hand here.
We then fixed a comment in the A01 mapping file on row 4 from "Processing of the MSH segment results in the creation of a new MessageHeader resource" to "Processing of the MSH segment results in the creation of a new MessageHeader resource." adding the missing period at the end.
We uploaded then the segment inventory file to see whether that picked up the message maps as well. We did not get as far as now we got a failure that seemed to be in SUSHI land.
When we uploaded a cleaned-up message inventory to gitHub it triggered the build and got a new IG. It did include 4575 errors, but seemed all to be similar. So that is not the problem at hand here.
We then fixed a comment in the A01 mapping file on row 4 from "Processing of the MSH segment results in the creation of a new MessageHeader resource" to "Processing of the MSH segment results in the creation of a new MessageHeader resource." adding the missing period at the end.
We uploaded then the segment inventory file to see whether that picked up the message maps as well. We did not get as far as now we got a failure that seemed to be in SUSHI land.
The report is here: https://build.fhir.org/ig/HL7/v2-to-fhir/branches/master/qa.html
The text was updated successfully, but these errors were encountered: