Quality assurance

input/ignoreWarnings.txt

@@ -2,4 +2,10 @@
 
 # Add warning and/or information messages here after you've confirmed that they aren't really a problem
 # (And include comments like this justifying why)
-# See https://github.com/FHIR/sample-ig/blob/master/input/ignoreWarnings.txt for examples
+# See https://github.com/FHIR/sample-ig/blob/master/input/ignoreWarnings.txt for examples
+
+# These examples are fake code systems - they're not expected to be checked
+Code System URI 'http://ownSystem.fi/CodeSystem/cs-insulincode' is unknown so the code cannot be validated
+Code System URI 'http://terminology.own.com' is unknown so the code cannot be validated
+Code System URI 'http://ownSystem.com/phr-cs-fitnesscategory' is unknown so the code cannot be validated
+Code System URI 'http://example.oma' is unknown so the code cannot be validated

input/pagecontent/Encounter-id-for-ward-encounter-intro.md

@@ -45,6 +45,3 @@ Querying by location is also an option. Here the focus is on the physical locati
 organizational responsibility towards the patient.
 [This blog post](https://fhirblog.com/2013/10/24/adventures-in-searching-getting-a-list-of-patients-in-a-ward/)
 will describe the process.
-
-See [the guide](StructureDefinition-fi-base-encounter-patients-in-ward.html) for how to fetch
-patients in a ward.

input/pagecontent/StructureDefinition-fi-base-encounter-intro.md

@@ -37,18 +37,19 @@ resource.
 
 First thing is to identify the appropriate aggregation level of encounter. If encounter is not
 representing a *palvelutapahtuma*, but is a lower level encounter (some systems call these
-*prosessitapahtuma*), parentOf -should be used to point to upper level encounter (up until
-*palvelutapahtuma* -level is reached).
+*prosessitapahtuma*), `partOf` should be used to point to upper level encounter (up until
+*palvelutapahtuma* level is reached).
 
-*Palvelutapahtuma* -encounter is identified by identifier. When encounter has identifier with
-`use=official` it SHOULD be considered as palvelutapahtuma and that identifier should be the
-OID of *palvelutapahtuma*.
+A *palvelutapahtuma* encounter is identified by identifier. When encounter has an identifier with
+`use=official` it is considered to be a *palvelutapahtuma* and that identifier SHALL be the
+OID of a *palvelutapahtuma*.
 
-Other levels of encounter that are not *palvelutapahtuma*, MUST NOT contain `use=official` identifier.
+Other levels of encounter that are not a *palvelutapahtuma*, MUST NOT contain an ientifier with
+`use=official`.
 
 #### Organizational responsibility
 
-The unit responsible for the encounter should be communicated using the `serviceProvider` property.
+The unit responsible for the encounter SHOULD be communicated using the `serviceProvider` property.
 
-For instance, there's a [detailed example with explanations](Encounter-id-for-ward-encounter.html)
-how to fetch patients in a ward.
+For instance, there's a [detailed example with explanations](Encounter-id-for-ward-encounter.html) 
+for how to fetch patients in a ward.

input/pagecontent/history.md

@@ -17,9 +17,17 @@ New snapshot versions will be published throughout the ballot cycle.
       </tr>
     </thead>
     <tbody>
+      <tr style="background-color: #f9f9f9">
+        <td colspan="4"><b>Current Versions</b></td>
+      </tr>
+      <tr style="background-color: #f9f9f9">
+        <td colspan="4"><b>STU 1 Sequence</b></td>
+      </tr>
+      <tr><td></td><td></td><td></td><td></td></tr>
       <tr style="background-color: #f9f9f9">
         <td colspan="4"><b>Release Candidates</b></td>
       </tr>
+      <tr><td></td><td></td><td></td><td></td></tr>
       <tr>
         <td><a href="https://www.hl7.fi/fhir/finnish-base-profiles/1.0-rc2/">2023-02-20</a></td>
         <td>1.0.0-rc2</td><td>Ballot version for STU release 1.0.0</td>

input/pagecontent/index.md

@@ -5,7 +5,9 @@ This implementation guide specifies the Finnish FHIR base profiles.
 It builds on top of the [International Patient Access](https://build.fhir.org/ig/HL7/fhir-ipa/)
 specification.
 
-The profiles are based on R4, [FHIR 4.0.1](http://hl7.org/fhir/R4/).
+This implementation guide is based on [FHIR R4](http://hl7.org/fhir/R4/). None of the features it
+uses are changed in [FHIR R4B](http://hl7.org/fhir/R4B/), so it can be used as is with R4B systems.
+There is no plan yet to base this implementation guide on [FHIR R5](http://hl7.org/fhir/R5/).
 
 #### Companion Specifications
 
@@ -193,10 +195,10 @@ document all different approaches used.
 The profiling work is performed in a project driven by [HL7 Finland](https://www.hl7.fi).
 See the
 [announcement](https://www.hl7.fi/hl7-fhir-profilointityo-kaynnistyy-tule-mukaan-vaikuttamaan-kansalliseen-tekemiseen/)
-(in Finnish), the [running
-memo](https://docs.google.com/document/d/1yNq6XMLhWJqi6OELQtWC1DFwdtD9CQulzVOfz-zZCko/edit#), and
-[some more details](https://fhir.fi). We warmly welcome new participants to the project. You may
-even be compensated for your efforts.
+(in Finnish), the
+[running memo](https://docs.google.com/document/d/1yNq6XMLhWJqi6OELQtWC1DFwdtD9CQulzVOfz-zZCko/edit#),
+and [some more details](https://fhir.fi). We warmly welcome new participants to the project. You
+may even be compensated for your efforts.
 
 The team involved in creating the first version of the specification includes
 * Arto Huusko, CGI Oyj
@@ -215,7 +217,7 @@ The team involved in creating the first version of the specification includes
 * Tero Pekkola, Esko Systems Oy
 
 Each published major version of this implementation guide goes through the ballot and voting
-processes of HL7 Finland.
+processes of HL7 Finland, and then represents the consensus view of the Finnish FHIR community.
 
 ### Collaboration
 

input/pagecontent/profiles.md

@@ -1,6 +1,10 @@
 Profiles set additional constraints for the FHIR base resources and help tighter interoperability
 between systems.
 
+### Global Profiles
+
+{% include globals-table.xhtml %}.
+
 ### Finnish Base Profiles
 
 This is the list of base profiles for FHIR resources for use in Finland, published and maintained

package-list.json

@@ -0,0 +1,30 @@
+{
+  "package-id" : "hl7.fhir.fi.base",
+  "title" : "Finnish Base Profiles",
+  "canonical": "https://hl7.fi/fhir/finnish-base-profiles",
+  "introduction" : "A core set of FHIR resources profiled for use in Finland, published and maintained by HL7 Finland",
+  "category" : "National Base",
+  "list": [
+    {
+      "version" : "current",
+      "desc" : "Continuous Integration Build (latest in version control)",
+      "path" : "https://fhir.fi/finnish-base-profiles/",
+      "status" : "ci-build",
+      "sequence" : "STU 1 Sequence",
+      "fhirversion" : "4.0.1",
+      "current": true
+    },
+    {
+      "version" : "1.0.0-rc2",
+      "date" : "2023-02-20",
+      "desc" : "Ballot version for 1.0.0",
+      "path" : "https://hl7.fi/fhir/finnish-base-profiles/1.0-rc2/",
+      "changes" : "Ballot version for STU 1 release",
+      "status" : "ballot",
+      "sequence" : "STU 1 Sequence",
+      "fhirversion" : "4.0.1",
+      "ci-build" : "https://fhir.fi/finnish-base-profiles/",
+      "current": false
+    }
+  ]
+}

publication-request.json

@@ -4,10 +4,10 @@
   "path" : "https://hl7.fi/fhir/finnish-base-profiles/1.0-rc12/",
   "mode" : "working",
   "status" : "draft",
-  "sequence" : "Releases",
+  "sequence" : "STU 1 Sequence",
   "desc" : "Ballot version for 1.0.0",
   "descmd" : "First ballot release, for STU version 1.0.0.",
-  "changes" : "First fixed release",
+  "changes" : "First official release",
   "title" : "Finnish Base Profiles",
   "ci-build" : "https://fhir.fi/finnish-base-profiles/",
   "category" : "National Base",

sushi-config.yaml

@@ -8,7 +8,7 @@ name: FinnishBaseProfiles
 title: Finnish Base Profiles
 description: A core set of FHIR resources profiled for use in Finland, published and maintained by HL7 Finland
 status: draft # draft | active | retired | unknown
-version: 1.0.0-rc12
+version: 1.0.0-rc13
 fhirVersion: 4.0.1 # https://www.hl7.org/fhir/valueset-FHIR-version.html
 copyrightYear: 2022+
 releaseLabel: ci-build # ci-build | draft | qa-preview | ballot | trial-use | release | update | normative+trial-use