picture sizes

WorldHealthOrganization · Jun 12, 2024 · 5429369 · 5429369
1 parent 46c5bfc
commit 5429369
Show file tree

Hide file tree

Showing 14 changed files with 21 additions and 22 deletions.
diff --git a/input/pagecontent/diagram_legend.md b/input/pagecontent/diagram_legend.md
@@ -29,7 +29,7 @@ The relations are represented by arrows
 
 - **Flows to**: A relationship where an activity (process) is followed by another activity
 
-<figure>
+<figure style = "width:90em; max-width:90%">
   {% include diagram-arrows.svg %}
 </figure>
 

diff --git a/input/pagecontent/dictionary.md b/input/pagecontent/dictionary.md
diff --git a/input/pagecontent/gov_concepts.md b/input/pagecontent/gov_concepts.md
@@ -19,7 +19,7 @@ See section "Semantic Compatibility Assessment" for more details.
 The introduction of concept management (by means of common data dictionaries) enables a more complete approach to semantic interoperability.
 
 Each concept in the Commons dictionary has therefore its definition and mappings:
-<figure>
+<figure style = "width:25em">
   {% include concept-dictionary.svg %}
   <figcaption>Concepts and Dictionary - metadata</figcaption>
 </figure>

diff --git a/input/pagecontent/ig_setup.md b/input/pagecontent/ig_setup.md
@@ -6,7 +6,7 @@ A SMART Guidelines Implementation Guide makes use of existing tooling and conten
 
 The key repositories that play a role are identified in the diagram below:
 
-<figure>
+<figure style = "width:90em; max-width:90%">
   {% include dependencies.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_codesystems.md b/input/pagecontent/l3_codesystems.md
@@ -4,7 +4,7 @@ In particular, each SMART guideline will have a guideline-level code system defi
 
 In addition, sometimes existing code systems need to be completed, for example adding designations in different languages to codes, or adding relationships between vaccine codes.
 
-<figure>
+<figure style = "width:25em">
   {% include model_codesystem.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_forms.md b/input/pagecontent/l3_forms.md
@@ -2,7 +2,7 @@ Data used in the different stages of the business processes can be captured from
 
 Since the purpose of the forms is to expose data in a user-friendly manner (and following the L2 DAK data structures), it is expected that several of these forms will result in the data being extracted to FHIR-native resources, like Patient, Observation, Condition, etc.
 This means the L2 data structures are represented both as instances Questionnaires and as FHIR resource profiles, and these FHIR resources can be obtained natively or by extracting a QuestionnaireResponse:
-<img src="./forms_resources.png" style="width:50%"/>
+<img src="./forms_resources.png" style="width:40%"/>
 <br clear="all"/>
 
 
@@ -12,12 +12,12 @@ SMART Guidelines make use of the [FHIR Structured Data Capture specification](ht
 * Data extraction
 
 Forms are reuse other forms and make use of value sets. 
-<figure>
+<figure style = "width:25em">
   {% include model_form.svg %}
 </figure>
 
 This extraction uses [structure maps](l3_structuremaps.html) and is represented as follows:
-<figure>
+<figure style = "width:75em; max-width:90%">
   {% include extraction.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_logicalmodels.md b/input/pagecontent/l3_logicalmodels.md
@@ -11,7 +11,7 @@ Logical models relate to other models in 3 aspects:
 
 
 Each Logical Model is defined by the following data:
-<figure style = "width:400px">
+<figure style = "width:30em">
   {% include model_logicalmodel.svg %}
 </figure>
 
@@ -24,9 +24,11 @@ Each Logical Model is defined by the following data:
 
 * Logical Models in `input/models` or `fsh/models`
 
-### **Activities:**
+### **Activities:**  
+
+This is the overview of the activities and related artifacts used:  
+
 
-This is the overview of the activities and related artifacts used:
 <img src="./l3_process_logicalmodel.png" style="width:50%"/>
 <br clear="all"/>
 

diff --git a/input/pagecontent/l3_personas.md b/input/pagecontent/l3_personas.md
@@ -1,7 +1,7 @@
 ActorDefinitions are the ways that the Personas are structured; A common repository of Personas allows reuse, exchange, change tracking, etc.  
 
 Each Persona is defined by the following data:
-<figure>
+<figure style = "width:15em">
   {% include model_persona.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_processes.md b/input/pagecontent/l3_processes.md
@@ -3,7 +3,7 @@ Business processes are structured into FHIR PlanDefinitions. This can be used to
 The L3 author must ensure there is a PlanDefinition for each Business Process mentioned in the L2. 
 
 The data required to be captured for each Business Process is:
-<figure>
+<figure style = "width:15em">
   {% include model_process.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_profiles.md b/input/pagecontent/l3_profiles.md
@@ -4,7 +4,7 @@ Profiles and extensions should be reusable as much as possible, and L3 authors s
 
 
 Profiles include Element constraints or extensions, and may include constraints:
-<figure>
+<figure style = "width:25em">
   {% include model_profile.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_requirements.md b/input/pagecontent/l3_requirements.md
@@ -6,7 +6,7 @@ Requirements - functional or non-functional - are captured as L3 artifacts for t
 The L3 author is expected to capture the requirements in a [Requirements](https://worldhealthorganization.github.io/smart-base/StructureDefinition-SGRequirements.html) resource.
 
 The requirements capture the following data:
-<figure>
+<figure style = "width:25em">
   {% include model_requirements.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_scenarios.md b/input/pagecontent/l3_scenarios.md
@@ -1,8 +1,8 @@
 Scenarios are uniquely identified "example stories" that describe how the system is expected to behave in a relatively concrete scenario. 
 
 
-Each Persona is defined by the following data:
-<figure>
+Each Scenario is defined by the following data:
+<figure style = "width:15em">
   {% include model_scenario.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_structuremaps.md b/input/pagecontent/l3_structuremaps.md
@@ -10,7 +10,7 @@ This process is done by 3 StructureMaps:
 * A grouping map that combines the two maps above to enable a single transform operation.
 
 
-<figure>
+<figure style = "width:50em">
   {% include extraction.svg %}
 </figure>
 
@@ -37,7 +37,7 @@ StructureMaps can be authored using the [FHIR Mapping Language](https://hl7.org/
 If a form is used, the L3 author should provide the mappings for extraction.
 
 * The StructureMap shall be saved as `input/resources/maps/<id>.fml` where id is the id of the map - not necessarily the name.
-<figure>
+<figure style = "width:15em">
   {% include model_structuremap.svg %}
 </figure>
 

diff --git a/input/pagecontent/l3_valuesets.md b/input/pagecontent/l3_valuesets.md
@@ -7,7 +7,7 @@ ValueSets are used in
 
 * The L3 should use same codes as defined for LM
 
-<figure>
+<figure style = "width:15em">
   {% include model_valueset.svg %}
 </figure>