From 7858974f9d7c13e09eac16d7f3cd6874d34e53c7 Mon Sep 17 00:00:00 2001 From: c-corman Date: Tue, 9 Jul 2024 16:40:03 +0300 Subject: [PATCH] Update of files from input --> pagecontent Updated the files that provide content for smart.who.int/dak-tb in order to align with TB DAK specific content and to reflect the current state of different artifacts --- input/pagecontent/adapting.md | 6 +- input/pagecontent/changes.md | 25 +- input/pagecontent/codings.md | 4 +- input/pagecontent/concepts.md | 235 +----------------- input/pagecontent/dependencies.md | 28 +-- input/pagecontent/downloads.md | 3 + input/pagecontent/indicators-measures.md | 4 +- input/pagecontent/maps.md | 4 +- input/pagecontent/personas.md | 16 +- .../pagecontent/reference-implementations.md | 5 +- input/pagecontent/references.md | 28 ++- input/pagecontent/scenarios.md | 13 +- input/pagecontent/security-privacy.md | 4 +- input/pagecontent/sequence-diagrams.md | 2 +- input/pagecontent/system-actors.md | 4 +- input/pagecontent/test-data.md | 2 + input/pagecontent/testing.md | 5 +- input/pagecontent/transactions.md | 3 + input/pagecontent/trust_domain.md | 2 + 19 files changed, 105 insertions(+), 288 deletions(-) diff --git a/input/pagecontent/adapting.md b/input/pagecontent/adapting.md index 34d0f223..3d4b7144 100644 --- a/input/pagecontent/adapting.md +++ b/input/pagecontent/adapting.md @@ -2,12 +2,12 @@ The following page provides a reference to resources that can guide countries in To implement WHO recommendations in country settings, governments must interpret and then adapt the content in line with local policies, procedures, and digital tools. -This implementation guide provides the generic content required in digital systems, independently of a specific software application and with the intention that countries can adapt it to meet local needs. +This implementation guide provides the generic content required in digital systems, software agnostic, with the intention that countries can adapt it to meet local needs. WHO guidelines articulate and endorse rigorously tested recommendations for health interventions to be adopted within country programs. When applied correctly and consistently, guideline recommendations save lives. To ensure that countries can effectively benefit from digital health investments, the SMART Guidelines approach is intended to facilitate the accurate reflection of WHO’s clinical, public health and data use guidelines in the digital systems that countries are adopting. For more on layers of knowledge representation and how they are used in WHO’s SMART Guidelines approach, see [WHO’s SMART Guidelines](https://www.who.int/teams/digital-health-and-innovation/smart-guidelines) and this [Lancet article](https://www.thelancet.com/journals/landig/article/PIIS2589-7500(21)00038-8/fulltext). -The standards-based technical artifacts in this implementation guide are at the third layer of knowledge representation (L3: Machine-readable recommendations). It provides code necessary for software developers to incorporate standardised logic from WHO guidelines into digital systems, testable for conformance to standards including fidelity to recommendations. A standards-based technical implementation guide builds on operational (L2) by mapping L2 content to value sets and Health Level Seven International Fast Healthcare Interoperability Resources (FHIR) standards. Alongside data standards from L2, this allows for semantic and syntactic interoperability at scale. The logic derived from guidelines, which might include clinical decision support and calculations for performance indicators, which may be encoded into Clinical Quality Language (CQL). This ensures that key indicators can be consistently extracted to support patient care, as well as case surveillance and programme monitoring. The machine-readable representations in this implementation guide are intended for adaptation into countries’ digital health service delivery and reporting systems. Digital solutions comprising L3 machine-readable recommendations may then be testable for conformance to interoperability standards. +The standards-based technical artifacts in this implementation guide are at the third layer of knowledge representation (L3: Machine-readable recommendations). It provides code necessary for software developers to incorporate standardised logic from WHO guidelines into digital systems, testable for conformance to standards including fidelity to recommendations. A standards-based technical implementation guide builds on operational (L2) by mapping L2 content to value sets and Health Level Seven International Fast Healthcare Interoperability Resources (FHIR) standards. Alongside data standards from L2, this allows for semantic and syntactic interoperability at scale. The logic derived from guidelines, which might include clinical decision support and calculations for performance indicators, may be encoded into Clinical Quality Language (CQL). This ensures that key indicators can be consistently extracted to support patient care, as well as case surveillance and programme monitoring. The machine-readable representations in this implementation guide are intended for adaptation into countries’ digital health service delivery and reporting systems. Digital solutions comprising L3 machine-readable recommendations may then be testable for conformance to interoperability standards. -The fourth layer (L4: Executable—reference applications and services) focuses on software applications and services within a digital ecosystem. It is intended to include executable reference software that accurately represents the intentions, operational, and functional requirements of the WHO recommendations; addresses user and health system needs; and comprises machine-readable data and calculations within interoperability standards, as documented in the L1–L3 layers. As a fully functional application, it is intended to serve as a generic starting point, ready to be localised to the specific operational context of the users, population, and health system within which it is deployed. Additional products at this layer include terminology services to support consistent data representation for interoperability; reusable software libraries including software development kits; application programming interfaces; and function as a service to support updates to FHIR content and capabilities across subscribed digital systems. \ No newline at end of file +The fourth layer (L4: Executable—reference applications and services) focuses on software applications and services within a digital ecosystem. It is intended to include executable reference software that accurately represents the intentions, operational, and functional requirements of the WHO recommendations; addresses user and health system needs; and comprises machine-readable data and calculations within interoperability standards, as documented in the L1–L3 layers. The fully functional applications referenced in L4 are intended to serve as a generic starting point for localization to the specific operational context of the users, population, and health system within which it is deployed. Additional products at this layer include terminology services to support consistent data representation for interoperability; reusable software libraries including software development kits; application programming interfaces; and function as a service to support updates to FHIR content and capabilities across subscribed digital systems. \ No newline at end of file diff --git a/input/pagecontent/changes.md b/input/pagecontent/changes.md index b77380b1..9b644f97 100644 --- a/input/pagecontent/changes.md +++ b/input/pagecontent/changes.md @@ -1,3 +1,26 @@ # SMART -Feel free to modify this index page with your own awesome content! \ No newline at end of file +*The following web pages were modified to align with TB DAK content and to reflect the current status of artifacts:* + +Home --> Changes +Home --> Dependencies +Home --> References +Home --> Adapting Guidelines for Country use + +Business requirements --> Concepts +Business requirements --> Generic Personas +Business requirements --> User Scenarios +Business requirements --> Business Processes + +Data Models and Exchange--> System actors +Data Models and Exchange--> Sequence Diagrams +Data Models and Exchange--> Transactions +Data Models and Exchange--> Indicators and Measures +Data Models and Exchange--> Codings + +Deployment --> Security and Privacy Considerations +Deployment --> Testing +Deployment --> Test data +Deployment --> Reference Implementations +Deployment --> Trust Domains +Deployment --> Downloads \ No newline at end of file diff --git a/input/pagecontent/codings.md b/input/pagecontent/codings.md index ce94c13f..a5303dd3 100644 --- a/input/pagecontent/codings.md +++ b/input/pagecontent/codings.md @@ -1,6 +1,6 @@ -Note that the terminologies included in this implementation guide will need to be updated, because the ideal mechanism for distribution (as an expression) is not currently supported by the content logical definition constructs available in the FHIR ValueSet resource and all known implementations of it. Before use in a production environment, ensure you have the latest value sets based on the definitions for each value set (as defined in the inclusion/exclusion criteria for each one). +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** -The following terminology artifacts are included for this implementation guide: +Note that the terminologies included in this implementation guide will need to be updated, because the ideal mechanism for distribution (as an expression) is not currently supported by the content logical definition constructs available in the FHIR ValueSet resource and all known implementations of it. Before use in a production environment, ensure you have the latest value sets based on the definitions for each value set (as defined in the inclusion/exclusion criteria for each one). ### CodeSystems {% include list-simple-codesystems.xhtml %} diff --git a/input/pagecontent/concepts.md b/input/pagecontent/concepts.md index 05dc384c..1340a8c3 100644 --- a/input/pagecontent/concepts.md +++ b/input/pagecontent/concepts.md @@ -1,235 +1,2 @@ -Key concepts and abbreviations are described here. Additional terms are defined in the Glossary and List of Abbreviations in the WHO Digital Adaptation Kit for [insert health domain here] (link forthcoming) -### Concepts +Please consult the "Glossary" section of the TB DAK for the key terms and the "Abbreviations" section for the abbreviations used in the DAK. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TermDescription
Anatomical Therapeutic Chemical code (ATC)A unique code assigned to a medicine according to the organ or system it works on and how it works.
CertificateA document attesting a fact. In the context of the vaccination certificate, it attests to the fact that a vaccine has been administered to an individual.
Clinical practice guidelines (CPG)Clinical practice guidelines are statements that include recommendations intended to optimize patient care that are informed by a systematic review of evidence and an assessment of the benefits and harms of alternative care options.
Clinical Quality Language (CQL)This is a HL7 specification for the expression of clinical knowledge that can be used within both the Clinical Decision Support (CDS) and Clinical Quality Measurement (CQM) domains.
Data dictionaryA centralized repository of information about the data elements that contains their definition, relationships, origin, usage, and type of data. For this digital adaptation kit, the data dictionary is provided as a spreadsheet.
Data elementA unit of data that has specific and precise meaning.
Fast Healthcare Interoperability Resources (FHIR)A standard describing data formats and elements and an application programming interface for exchanging electronic health records.
Functional requirementCapabilities the system must have in order to meet the end-users’ needs and achieve tasks within the business process.
Implementation Guide (IG)A set of rules about how FHIR resources are used (or should be used) to solve a particular problem, with associated documentation to support and clarify the usage. This IG is based on WHO guidance, as it is represented in the Digital Adaptation Kit for [insert health domain here], to support the adoption of open standards for interoperability.
IndicatorSummary measures that capture relevant information on different attributes and dimensions of health status and performance of a health system.
International Patient Summary (IPS)An electronic health record extract containing essential healthcare information about a client.
Non-functional requirementGeneral attributes and features of the digital system to ensure usability and overcome technical and physical constraints. Examples of non-functional requirements include ability to work offline, multiple language settings, and password protection.
Systemized Nomenclature of Medicine – Clinical Terms Global Patient Set (SNOMED CT GPS)A systematically organized computer-processable collection of medical terms providing codes, terms, synonyms and definitions used in clinical documentation and reporting.
- -### Abbreviations - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TermDescription
BPMNBusiness Process Model and Notation
CDCCenters for Disease Control and Prevention
CDSClinical decision support
CHWCommunity health worker
CQLClinical Quality Language
DAKDigital Adaptation Kit
DEData element
DMNDecision Model and Notation
DTDecision support table
DTDSDigital tracking and decision support
EDEvent-driven
eHealthElectronic health
EMRElectronic medical record
FHIRFast Healthcare Interoperability Resources
HWHealth Worker
HL7Health Level Seven International
HMISHealth management information system
ICDInternational Classification of Diseases
ICD-11International Classification of Diseases (version 11)
ICFInternational Classification of Functioning, Disability and Health
ICHIInternational Classification of Health Interventions
IDIdentification
IGImplementation guide
IHEIntegrating the Healthcare Enterprise
ISCOInternational Standard for Classification of Occupations
ITUInternational Telecommunication Union
LOINCLogical Observation Identifiers Names and Codes
M&EMonitoring and Evaluation
MAPSmHealth Assessment and Planning for Scale
mHealthMobile Health
MOHMinistry of Health
NMFLNational Master Facility List
NFXNREQNon-functional requirement
OpenHIEOpen Health Information Exchange
PrEPpre-exposure prophylaxis
SMARTStandards-based, Machine-readable, Adaptive, Requirements-based and Testable
SNOMED CTSystematized Nomenclature of Medicine - Clinical Terms
VVMVaccine Vial Monitor
WHOWorld Health Organization
diff --git a/input/pagecontent/dependencies.md b/input/pagecontent/dependencies.md index 453a2f92..b2a7de51 100644 --- a/input/pagecontent/dependencies.md +++ b/input/pagecontent/dependencies.md @@ -1,19 +1,15 @@ -The following standards and profiles are referenced in this implementation guide: -* Integrating the Healthcare Enterprise (IHE): +The following standards are referenced in this implementation guide: - * [Audit Trail and Node Authentication (ATNA) Profile](https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html) +** Standardized terminologies and classifications:** - * [Sharing Valuesets and Concept Maps (SVCM) Profile](https://profiles.ihe.net/ITI/SVCM/index.html) - - * [Mobile Care Services Discovery (mCSD) Profile](https://profiles.ihe.net/ITI/mCSD/index.html) - -* The International Patient Summary (IPS): - - * [Health Level 7 (HL7) Fast Healthcare Interoperability Resources (FHIR) IPS Implementation Guide, published by HL7 International - Patient Care Work Group](http://hl7.org/fhir/uv/ips/index.html) - -* World Health Organization (WHO): - - * [WHO International Classification of Diseases 11th Revision (ICD-11)](https://icd.who.int/en) - - * [WHO Family of International Classifications](https://www.who.int/standards/classifications) \ No newline at end of file + * [WHO Family of International Classifications](https://www.who.int/standards/classifications) + + - [WHO International Classification of Diseases 11th Revision (ICD-11)](https://icd.who.int/browse/2024-01/mms/en) + - [International Statistical Classification of Diseases and Related Health Problems 10th Revision (ICD-10)] (https://icd.who.int/browse10/2019/en) + - [International Classification of Functioning, Disability and Health (ICF)] (https://icd.who.int/dev11/l-icf/en) + - [International Classification of Health Interventions (ICHI)] (https://icd.who.int/dev11/l-ichi/en) + + * [LOINC version 2.73](https://loinc.org/news/loinc-version-2-73-is-now-available/) + + * [SNOMED GPS] (https://www.snomed.org/gps) \ No newline at end of file diff --git a/input/pagecontent/downloads.md b/input/pagecontent/downloads.md index aff16cb0..a6053f67 100644 --- a/input/pagecontent/downloads.md +++ b/input/pagecontent/downloads.md @@ -1,3 +1,6 @@ + +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** + ### Package This is the technical package containing the artifacts in this Implementation Guide: diff --git a/input/pagecontent/indicators-measures.md b/input/pagecontent/indicators-measures.md index 33e1b6b8..aa4b26a2 100644 --- a/input/pagecontent/indicators-measures.md +++ b/input/pagecontent/indicators-measures.md @@ -1,8 +1,10 @@ +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** + The FHIR Measure is used to describe the indicator in a computable format. These indicators may be aggregated automatically from the digital tracking tool to populate a digital health management information system (HMIS). Measures included in this implementation guide are listed in the [Artifact Index - Measures](artifacts.html) -For the operational descriptions of indicators and references, see the Digital Adaptation Kit (DAK) for [insert health domain here], including Web Annex C of the DAK. Summary indicator content from the DAK is also represented in the Indicators and Performance Metrics page. +For the operational descriptions of indicators and references, see Indicators and Performance Metrics page. diff --git a/input/pagecontent/maps.md b/input/pagecontent/maps.md index 977a7b71..44934208 100644 --- a/input/pagecontent/maps.md +++ b/input/pagecontent/maps.md @@ -1 +1,3 @@ -# Mappings \ No newline at end of file +# Mappings + +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** \ No newline at end of file diff --git a/input/pagecontent/personas.md b/input/pagecontent/personas.md index 342c2550..1ba7dda9 100644 --- a/input/pagecontent/personas.md +++ b/input/pagecontent/personas.md @@ -1,17 +1,11 @@ -This page includes a depiction of end-users and related stakeholders as introduced in the WHO Digital Adaptation Kit for [insert health domain here](link forthcoming). +A persona is a depiction of a relevant stakeholder, or end user, of the system. -The specific roles and demographic profile of the personas will vary depending on the setting, the generic personas are based on the WHO core competencies and credentials of different health worker personas. +Although the specific roles and demographic profiles of the personas will vary depending on the setting, generic personas are based on WHO core competencies and credentials of different health worker personas. ### Targeted generic personas -The targeted personas for the [insert health domain here] Digital Adaptation Kit are -health professionals operating in care settings that are able to provide -the required essential interventions for [insert health domain here] delivery. Their -key competences of are defined in the following table. +In the case of TB, physicians, nurses and clinical officers are the primary personas for the digital client health record and decision-support system. In the health systems surveyed for this DAK, the common combination of service providers was a physician along with a nurse. The key competences of physicians, nurses and clinical officers are defined by WHO in the Table 2 of the DAK. -**Descriptions of key generic personas** - -{% include fragment-actors.liquid %} - -
\ No newline at end of file +### Related personas +In addition to the targeted personas detailed in Table 2, there may be value in exploring other cadres and personas within the context of TB services, such as laboratory technicians or community health workers. However, these were not identified as the central personas for the data and decision-support content detailed in this DAK. Additional related personas are listed in the Table 3 of the DAK. diff --git a/input/pagecontent/reference-implementations.md b/input/pagecontent/reference-implementations.md index cdb601fd..a57df463 100644 --- a/input/pagecontent/reference-implementations.md +++ b/input/pagecontent/reference-implementations.md @@ -1,4 +1,7 @@ -This page includes sample resources that can be leveraged to support the implementation of SMART Guidelines for [insert health domain here]. Content is for demonstration purposes only. + +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** + +This page will include sample resources that can be leveraged to support the implementation of SMART Guidelines for TB. Content is for demonstration purposes only. Additional relevant resources are included in the References and Dependencies. diff --git a/input/pagecontent/references.md b/input/pagecontent/references.md index 14043499..46e2453c 100644 --- a/input/pagecontent/references.md +++ b/input/pagecontent/references.md @@ -1,12 +1,23 @@ -This implementation guide is meant to facilitate operationalization of the World Health Organization (WHO) Digital Adaptation Kit (DAK) for [insert health domain here]. This page includes links to the published DAK for [insert health domain here], as well as a small subset of other references. +This implementation guide is meant to facilitate operationalization of the World Health Organization (WHO) Digital Adaptation Kit (DAK) for tuberculosis (TB). -For additional resources, see the Dependencies page, which includes the standards referenced in this implementation guide and the references section in the published DAK for [insert health domain here]. +The DAK for TB and the associated implementation tools can be found here: -### WHO Digital Adaptation Kit (DAK) for [insert health domain here] +- [Published DAK Document](https://iris.who.int/handle/10665/376631) -> The Digital Adaptation Kit was published on \[publication date\]: -> -> \[Link to the DAK and accompanying web annexes when available\] +- Implementation tools: + + - [Link to core data dictionary](https://smart.who.int/dak-tb/dictionary.html) + + - [Link to decision support logic](https://smart.who.int/dak-tb/decision-logic.html) + + - [Link to scheduling logic](https://smart.who.int/dak-tb/scheduling-logic.html) + + - [Link to indicators table](https://smart.who.int/dak-tb/indicators.html) + + - [Link to functional and non functional requirements](https://smart.who.int/dak-tb/system-requirements.html) + + +For additional resources, see the Dependencies page, which includes the standards referenced in this implementation guide, and the references section in the published DAK for TB. ### WHO guideline development @@ -17,7 +28,4 @@ For additional resources, see the Dependencies ### Tutorials and reference materials for developers - [References section of the SMART IG starter kit](https://worldhealthorganization.github.io/smart-ig-starter-kit/references.html#2) -### Additional resources -- [WHO Digital implementation investment guide (DIIG): integrating digital interventions into health programmes](https://www.who.int/publications/i/item/9789240010567) - -- [Open Health Information Exchange (OpenHIE) Specification and Architecture](https://guides.ohie.org/arch-spec/architecture-specification/overview-of-the-architecture) +- [Open Health Information Exchange (OpenHIE) Specification and Architecture](https://guides.ohie.org/arch-spec/architecture-specification/overview-of-the-architecture) diff --git a/input/pagecontent/scenarios.md b/input/pagecontent/scenarios.md index 44f448f3..9283e153 100644 --- a/input/pagecontent/scenarios.md +++ b/input/pagecontent/scenarios.md @@ -1,7 +1,16 @@ -Component 3 in the Digital Adaptation Kit (link forthcoming) includes user scenarios, which are narratives that describe how the different personas may interact with each other. The user scenarios are only illustrative and are intended to give an idea of a typical workflow. +Component 3 in the Digital Adaptation Kit includes user scenarios, which are narratives that describe how the different personas may interact with each other and with the digital system. The user scenario is provided to help the reader better understand how the system will be used and how it would fit into existing workflows. + +The TB DAK includes 7 scenarios grouped into: +- User scenarios for tuberculosis screening and tuberculosis preventive treatment; +- User scenarios for tuberculosis diagnosis and treatment. + +Please consult chapter 3 from TB DAK where all scenarios are presented. **How to interpret user scenarios** User scenarios can be helpful tools not only to better understand the context in which a digital tool would operate, but also for some insights into what key data elements would need to be recorded and accounted for in the database. Additionally, the context in which the tool would operate, illuminated by the user scenarios, provides insight into some functional and non-functional requirements that the system would also need. -As examples, the scenarios identify: key data elements that need to be recorded and/or calculated; decision-support logic that can be automated in the system; key functional and non-functional requirements that should be included in the system, and adolescent-specific considerations that should be accounted for. +As examples, the scenarios identify: +- key data elements that need to be recorded and/or calculated; +- decision-support logic that can be automated in the system; +- key functional and non-functional requirements that should be included in the system. diff --git a/input/pagecontent/security-privacy.md b/input/pagecontent/security-privacy.md index 622f5c04..a6cdff0c 100644 --- a/input/pagecontent/security-privacy.md +++ b/input/pagecontent/security-privacy.md @@ -1,3 +1,3 @@ -This page will contain security and privacy considerations related to SMART Guidelines for [insert health domain here]. +This page contain security and privacy considerations related to SMART Guidelines for TB. -For an illustrative, starting set of non-functional requirements, which includes security and privacy-related requirements from the Digital Adaptation Kit for [insert health domain here], see the [Non-functional Requirements](non-functional-requirements.html). \ No newline at end of file +For an illustrative, starting set of non-functional requirements, which includes security and privacy-related requirements from the Digital Adaptation Kit for TB, see the [Non-functional Requirements](non-functional-requirements.html). \ No newline at end of file diff --git a/input/pagecontent/sequence-diagrams.md b/input/pagecontent/sequence-diagrams.md index b77380b1..50027ac1 100644 --- a/input/pagecontent/sequence-diagrams.md +++ b/input/pagecontent/sequence-diagrams.md @@ -1,3 +1,3 @@ # SMART -Feel free to modify this index page with your own awesome content! \ No newline at end of file +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** \ No newline at end of file diff --git a/input/pagecontent/system-actors.md b/input/pagecontent/system-actors.md index 583f7823..13c712a3 100644 --- a/input/pagecontent/system-actors.md +++ b/input/pagecontent/system-actors.md @@ -1,4 +1,6 @@ -This page lists and describes the human users and digital services that interact with the system, derived from the business requirements defined at the operational level (L2). For more details about end-users and related stakeholders, see the [Generic Personas](personas.html) and the WHO Digital Adaptation Kit for [insert health domain here](link forthcoming). +This page is intended to list and describe the system actors that interact with the system, derived from the business requirements defined at the operational level (L2). This content is not yet available. The page will be updated once the system actors are defined. + +For more details about end-users and related stakeholders, see the [Generic Personas](personas.html). Systems managing clinical and patient information are expected to interact with a shared health record, laboratory information system or a longitudinal health record, as appropriate, and to synchronize with data collected in a clinical encounter. diff --git a/input/pagecontent/test-data.md b/input/pagecontent/test-data.md index b957ee52..239b357f 100644 --- a/input/pagecontent/test-data.md +++ b/input/pagecontent/test-data.md @@ -1,3 +1,5 @@ +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** + This page will include test data developed for the test scenarios and actors included in this implementation guide. See [Testing](testing.html) for additional testing artifacts. The testing artifacts in this implementation guide are not intended to be used to determine formal conformance, nor are they intended to be authoritative or comprehensive. \ No newline at end of file diff --git a/input/pagecontent/testing.md b/input/pagecontent/testing.md index 4dced900..245f054b 100644 --- a/input/pagecontent/testing.md +++ b/input/pagecontent/testing.md @@ -5,16 +5,17 @@ {% assign resource = site.data.resources[resourceKey] %} {% assign source = resource.source %} +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** + This page will include testing artifacts for this implementation guide. Artifacts will include Gherkin .feature files, with acceptance criteria for each test definition, and with defined test cases for PlanDefinitions and Measures. Example data will be in the form of FHIR shorthand (FSH) files or FHIR Resources, with examples listed under the example tab of the resources. -See [Test Data](test-data.html) for test data. +Test data will be added in [Test Data](test-data.html) page. The testing artifacts in this implementation guide are not intended to be used to determine formal conformance, nor are they intended to be authoritative or comprehensive. - ### Testing platforms diff --git a/input/pagecontent/transactions.md b/input/pagecontent/transactions.md index 465f8ae3..05be33f5 100644 --- a/input/pagecontent/transactions.md +++ b/input/pagecontent/transactions.md @@ -1,3 +1,6 @@ + +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** + This page will describe transactions with trigger events, message semantics, and expected actions, as well as sequence diagrams. See the [Digital Documentation of COVID-19 Certificates (DDCC) Transactions](https://worldhealthorganization.github.io/ddcc/transactions.html) for additional transactions that may be relevant. diff --git a/input/pagecontent/trust_domain.md b/input/pagecontent/trust_domain.md index fb734396..5dfe8ecc 100644 --- a/input/pagecontent/trust_domain.md +++ b/input/pagecontent/trust_domain.md @@ -1,3 +1,5 @@ +**This content is not yet available. The page will be updated as soon as the content is ready to be shared.** + ### Use Cases {% include trust_domain_use_cases.md %}