Canonical Resource Management Infrastructure Implementation Guide
1.0.0 - STU1

Publication Build: This will be filled in by the publication tooling

## Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

### Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

CRMI Artifact Terminology Service | Capability statement for a terminology service supporting artifact authoring and evaluation use cases. A server can support more functionality than defined here, but this defines the minimum expectations.
CRMI Authoring Artifact Repository | Capability statement for a repository service supporting additional authoring and content workflow capabilities for FHIR-based knowledge artifacts above the basic ShareableArtifactRepository.
CRMI Publishable Artifact Repository | Capability statement for a repository service supporting additional publishing capabilities for FHIR-based knowledge artifacts above the basic ShareableArtifactRepository.
CRMI Shareable Artifact Repository | Capability statement for a repository service supporting minimum required capabilities to share FHIR-based artifact specifications. See the Publishable and Authoring Artifact Repository capability statements for more comprehensive support for publishing and authoring workflows.

### Behavior: Operation Definitions

These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.

CRMI Approve Operation | The approve operation supports applying an approval to an existing artifact, regardless of status. The operation sets the date and approvalDate elements of the approved artifact, and is otherwise only allowed to create ArtifactAssessment (Basic or cqf-artifactComment extensions in R4) resources in the repository.
CRMI Artifact Diff Operation | Describes the differences between two knowledge artifacts in FHIR Patch format by recursively resolving dependencies to get a holistic diff.
CRMI Clone Operation | Creates a clone version of a knowledge artifact, as well as for all resources it is composed of.
CRMI Data Requirements Operation | Determines the effective data requirements for the artifact, including known components and dependencies, and optionally informed by a version manifest. See $package and $data-requirements
CRMI Draft Operation | Creates a draft version of a knowledge artifact, as well as for all resources it is composed of.
CRMI Extension of Value Set Expansion | The definition of a value set is used to create a simple collection of codes suitable for use for data entry or validation. If the operation is not called at the instance level, one of the in parameters url, context or valueSet must be provided. An expanded value set will be returned, or an OperationOutcome with an error message.
CRMI Package Operation | Packages a specified canonical resource for use in a target environment, optionally including related content such as dependencies, components, and testing cases and data. See $package and $data-requirements
CRMI Profiled Operation Example | This operation definition is a copy of the CRMI Data Requirements operation but declaring conformance to the CRMI Artifact, Artifact Version Bindable, Artifact Endpoint Configurable, and Manifestable operation profiles.
CRMI Release Operation | The release operation supports updating the status of an existing draft artifact to active. The operation sets the date element of the resource and pins versions of all direct and transitive references and records them in the program’s manifest. Child artifacts (i.e. artifacts of which the existing artifact is composed) are also released, recursively.
CRMI Review Operation | The review operation supports applying an review to an existing artifact, regardless of status. The operation sets the date and lastReviewDate elements of the reviewed artifact, and is otherwise only allowed to create ArtifactAssessment (Basic or cqf-artifactComment extension in R4) resources in the repository.
Example of a Canonical Version Bindable and Pageable Operation Definition | This operation definition is a copy of the CRMI ValueSet/$expand OperationDefinition that declares conformance to the CRMI Canonical Version Bindable and CRMI Pageable operation profiles
Get Package | Retrieves a FHIR package given the package id and version.

### Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

CRMI Computable Library | The CRMI Computable Library profile defines the must support elements for a computable library used to support artifact logic
CRMI Computable ValueSet | Defines a computable value set as one that SHALL have an expression-based definition (i.e. a value set defined intensionally using expressions of the code systems involved) and MAY have an expansion included. The expression-based definition SHALL be represented in only one of three ways; using the compose element, using the expression extension, or using the rules-text extension to provide a step-by-step process for expanding the value set definition
CRMI Evaluation Result Parameters | The CRMI Evaluation Result Parameters Profile supports using the dataAbsentReason extension to indicate null evaluation results from operations.
CRMI Executable Library | The CRMI Execuable Library profile defines the must support elements for an executable library used to support artifact logic
CRMI Expanded ValueSet | Defines an expanded value set as one that SHALL have an expansion included, as well as a usage warning indicating the expansion is a point-in-time snapshot and must be maintained over time for production usage. The value set expansion specifies the timestamp when the expansion was produced, SHOULD contain the parameters used for the expansion, and SHALL contain the codes that are obtained by evaluating the value set definition. If this is ONLY an expanded value set, a computable definition of the value set must be obtained to compute the updated expansion.
CRMI GroupDefinition | Represents the definition of a group of subjects, suitable for use in various contexts, such as a cohort definition, a recommendation inclusion or exclusion criteria, the members of a study, or a population criteria
CRMI ImplementationGuide | Supports the specification of expansion parameters to be used with the implementation guide
CRMI Manifest Library | Defines and supports the definition of a manifest used to establish specific versions of dependencies used in a collection of knowledge artifacts
CRMI MedicationDefinition | Represents the definition of a medication, suitable for use in various contexts
CRMI MedicationKnowledge Definition | Represents the definition of medication knowledge, suitable for use in various contexts
CRMI Module Configuration Library | The CRMI Module Configuration Library profile supports configuration of the data requirements for a module for a given endpoint. This is useful to provide endpoint-specific configuration of the queries to be used to gather data to satisfy the data requirements for a given module
CRMI Module Definition Library | The CRMI Module Definition Library profile defines the must support elements for a library that communicates the effective data requirements and dependencies of an artifact (or set of artifacts). This is most commonly used as the result of a $data-requirements operation, but could also be persisted statically as a way to persist the calculation of effective data requirements for a specific artifact and input parameters
CRMI Operation Profile: Artifact Endpoint Configurable | Profile for operations where artifact endpoint configuration can be specified. `artifactEndpointConfiguration`: Configuration information to resolve canonical artifacts `artifactRoute`: An optional route used to determine whether this endpoint is expected to be able to resolve artifacts that match the route (i.e. start with the route, up to and including the entire url) `endpointUri`: The URI of the endpoint, exclusive with the `endpoint` parameter `endpoint`: An Endpoint resource describing the endpoint, exclusive with the `endpointUri` parameter Processing semantics: Create a canonical-like reference (e.g. `{canonical.url}|{canonical.version}` or similar extensions for non-canonical artifacts). Given a single `artifactEndpointConfiguration` When `artifactRoute` is present And `artifactRoute` starts with canonical or artifact reference Then attempt to resolve with `endpointUri` or `endpoint` When `artifactRoute` is not present Then attempt to resolve with `endpointUri` or `endpoint` Given multiple `artifactEndpointConfiguration`s Then rank order each configuration (see below) And attempt to resolve with `endpointUri` or `endpoint` in order until resolved Rank each `artifactEndpointConfiguration` such that: if `artifactRoute` is present and `artifactRoute` starts with canonical or artifact reference: rank based on number of matching characters if `artifactRoute` is not present: include but rank lower NOTE: For evenly ranked `artifactEndpointConfiguration`s, order as defined in the OperationDefinition.
CRMI Operation Profile: Artifact Operation | Profile for knowledge artifact operations. This establishes input parameters when the operation is involked at the resource type level. The parameters are used to identify or specify the resource for the operation. `url`: artifact URL&ast; for the resource `version`: artifact version&ast; for the resource `identifier`: business identifier for the resource `resource`: instance of a canonical resource &ast;The artifact URL for canonical resources is `.url`, for non-canonical resources, it is the extension `artifact-url`. The version for canonical resources is `.version`, for non-canonical resources it is the extension `artifact-version`. NOTE: When invoking canonical operations using any combination of `url`, `version`, and `identifier`: if there is one-and-only-one matching resource, the operation should apply, otherwise an error state. if `resource` is specified then `url`, `version`, and `identifier` should be ignored.
CRMI Operation Profile: Artifact Version Bindable | Operation where default artifact version(s) can be specified. NOTE: Artifacts include FHIR Canonical resources and the resources specified as non-canonical resources, such as: Medication, Substance, MedicationKnowledge, and Group. `artifactVersion`: Specifies a version to use for a artifact resource if the artifact referencing the resource does not already specify a version. The format is the same as a canonical URL: `[url]|[version]` - e.g. `http://loinc.org|2.56` `checkArtifactVersion`: Edge Case: Specifies a version to use for a artifact resource. If the artifact referencing the resource specifies a different version, an error is returned instead of the package. The format is the same as a canonical URL: `[url]|[version]` - e.g. `http://loinc.org|2.56` `forceArtifactVersion`: Edge Case: Specifies a version to use for a artifact resource. This parameter overrides any specified version in the artifact (and any artifacts it depends on). The format is the same as a canonical URL: `[system]|[version]` - e.g. `http://loinc.org|2.56`. Note that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is both wrong and unsafe, and implementers should only use this capability reluctantly.
CRMI Operation Profile: Canonical Version Bindable | Operation where default canonical version(s) can be specified NOTE: This profile is here for backwards compatibility, see ArtifactVersionBindableOperation profile as a successor. `canonicalVersion`: Specifies a version to use for a canonical resource if the artifact referencing the resource does not already specify a version. The format is the same as a canonical URL: `[url]|[version]` - e.g. `http://loinc.org|2.56` `checkCanonicalVersion`: Edge Case: Specifies a version to use for a canonical resource. If the artifact referencing the resource specifies a different version, an error is returned instead of the package. The format is the same as a canonical URL: `[url]|[version]` - e.g. `http://loinc.org|2.56` `forceCanonicalVersion`: Edge Case: Specifies a version to use for a canonical resource. This parameter overrides any specified version in the artifact (and any artifacts it depends on). The format is the same as a canonical URL: `[system]|[version]` - e.g. `http://loinc.org|2.56`. Note that this has obvious safety issues, in that it may result in a value set expansion giving a different list of codes that is both wrong and unsafe, and implementers should only use this capability reluctantly.
CRMI Operation Profile: Manifestable | Operation where default manifest to resolve canonicals can be specified `manifest`: Canonical reference to a Library resource where related-artifacts are used to define the versions of canonical resources.
CRMI Operation Profile: Pageable | Operation that is pageable This establishes input parameters when the operation might return paging. `offset`: Pagination offset `count`: Number of items per page
CRMI Publishable ActivityDefinition | Supports declaration of the ActivityDefinition metadata required by HL7 and other organizations that share and publish activity definitions with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable CapabilityStatement | Supports declaration of the CapabilityStatement metadata required by HL7 and other organizations that share and publish capability statements with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable CodeSystem | Defines and enforces the minimum expectations for publication and distribution of a code system, typically as part of an artifact repository or implementation guide publication
CRMI Publishable ConceptMap | Defines and enforces the minimum expectations for publication and distribution of a concept map, typically as part of an artifact repository or implementation guide publication
CRMI Publishable GraphDefinition | Supports declaration of the GraphDefinition metadata required by HL7 and other organizations that share and publish graph definitions with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable ImplementationGuide | Supports declaration of the ImplementationGuide metadata required by HL7 and other organizations that share and publish implementation guides with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable Library | Supports declaration of the library metadata required by HL7 and other organizations that share and publish libraries with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable Measure | Supports declaration of the Measure metadata required by HL7 and other organizations that share and publish measures with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable NamingSystem | Defines and enforces the minimum expectations for publication and distribution of a naming system, typically as part of an artifact repository or implementation guide publication
CRMI Publishable OperationDefinition | Supports declaration of the OperationDefinition metadata required by HL7 and other organizations that share and publish operation definitions with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable PlanDefinition | Supports declaration of the PlanDefinition metadata required by HL7 and other organizations that share and publish plandefinitions with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable Questionnaire | Supports declaration of the Questionnaire metadata required by HL7 and other organizations that share and publish questionnaires with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable SearchParameter | Supports declaration of the SearchParameter metadata required by HL7 and other organizations that share and publish search parameters with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable StructureDefinition | Supports declaration of the StructureDefinition metadata required by HL7 and other organizations that share and publish structure definitions with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable TerminologyCapabilities | Supports declaration of the TerminologyCapabilities metadata required by HL7 and other organizations that share and publish terminology capabilities with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
CRMI Publishable ValueSet | Defines and enforces the minimum expectations for publication and distribution of a value set, typically as part of an artifact repository or implementation guide publication
CRMI Shareable ActivityDefinition | Enforces the minimum information set for the activity definition metadata required by HL7 and other organizations that share and publish activity definitions
CRMI Shareable CapabilityStatement | Enforces the minimum information set for the capabilitystatement metadata required by HL7 and other organizations that share and publish capability statements
CRMI Shareable CodeSystem | Enforces the minimum information set for the code system metadata required by HL7 and other organizations that share and publish code systems
CRMI Shareable ConceptMap | Enforces the minimum information set for the concept map metadata required by HL7 and other organizations that share and publish concept maps
CRMI Shareable GraphDefinition | Enforces the minimum information set for the graph definition metadata required by HL7 and other organizations that share and publish graph definitions
CRMI Shareable ImplementationGuide | Enforces the minimum information set for the implementation guide metadata required by HL7 and other organizations that share and publish implementation guides
CRMI Shareable Library | Enforces the minimum information set for the library metadata required by HL7 and other organizations that share and publish libraries
CRMI Shareable Measure | Enforces the minimum information set for the measure metadata required by HL7 and other organizations that share and publish measures
CRMI Shareable NamingSystem | Enforces the minimum information set for the naming system metadata required by HL7 and other organizations that share and publish naming systems
CRMI Shareable OperationDefinition | Enforces the minimum information set for the operation definition metadata required by HL7 and other organizations that share and publish operation definitions
CRMI Shareable PlanDefinition | Enforces the minimum information set for the plan definition metadata required by HL7 and other organizations that share and publish plan definitions
CRMI Shareable Questionnaire | Enforces the minimum information set for the questionnaire metadata required by HL7 and other organizations that share and publish questionnaires
CRMI Shareable SearchParameter | Enforces the minimum information set for the search parameter metadata required by HL7 and other organizations that share and publish search parameters
CRMI Shareable StructureDefinition | Enforces the minimum information set for the structure definition metadata required by HL7 and other organizations that share and publish structure definitions
CRMI Shareable TerminologyCapabilities | Enforces the minimum information set for the terminology capabilities metadata required by HL7 and other organizations that share and publish terminology capabilities
CRMI Shareable ValueSet | Enforces the minimum information set for the value set metadata required by HL7 and other organizations that share and publish value sets
CRMI Software System Device | The Software System device profile is used to capture software details about the various systems used in authoring, testing, packaging, or evaluation of a knowledge artifact
CRMI SubstanceDefinition | Represents the definition of a substance, suitable for use in various contexts

### Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

CRMI Configuration Endpoint | Which endpoint this module configuration is for
CRMI Configuration For | Which artifact this module configuration is for
CRMI Effective Data Requirements | A module definition library that contains the effective data requirements for an artifact (i.e. the calculated data requirements for the expressions directly referenced by the artifact structure).
CRMI Endpoint Supports POST | Indicates whether the endpoint of the configuration library on which it appears supports using a POST for search
CRMI Software System | Specifies the software systems used in the packaging and testing of knowledge artifacts. Specifically to support explicitly stating which versions of the various software components were used in the authoring, packaging, and testing.

### Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Artifact Resource Types | FHIR canonical plus knowledge artifact resource types.
CRMI Release Experimental Behavior | Behaviors of ‘experimentalBehavior’ parameter application in the $release operation.
CRMI Release Version Behavior | Behaviors of ‘version’ parameter application in the $release operation.

### Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

CRMI Release Experimental Behavior Codes | Behaviors of ‘experimentalBehavior’ parameter application in the $release operation.
CRMI Release Version Behavior Codes | Behaviors of ‘version’ parameter application in the $release operation.

### Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

ANC Cohort | Cohort definition for antenatal care
ANC.B5 Quick check (Publishable Example) | Quick check questionnaire
ANC.B5 Quick check (Shareable Example) | Quick check questionnaire
ANC.DT.01 Danger signs (Publishable Example) | Before each contact, during the Quick Check, the health worker should check whether the woman has any of the danger signs listed here – if yes, she should be referred to the hospital urgently; if no, the normal contact should be continued as normal
ANC.DT.01 Danger signs (Shareable Example) | Before each contact, during the Quick Check, the health worker should check whether the woman has any of the danger signs listed here – if yes, she should be referred to the hospital urgently; if no, the normal contact should be continued as normal
ANC.IND.01 Percentage of pregnant women with first ANC contact in the first trimester (Publishable Example) | Percentage of pregnant women with first ANC contact in the first trimester (before 12 weeks of gestation)
ANC.IND.01 Percentage of pregnant women with first ANC contact in the first trimester (Shareable Example) | Percentage of pregnant women with first ANC contact in the first trimester (before 12 weeks of gestation)
ANCM Activity Codes (Shareable Example) | Set of codes representing all activities used in the implementation guide
ANCM Concept Codes (Publishable Example) | Set of codes representing all concepts used in the implementation guide
ANCM Danger Signs Package | This library is an example of an artifact manifest for the DT-01 PlanDefinition from the ANC-Mini IG.
CQF Tooling Device | Example of a Software System Device instance for describing tooling that was used to process artifacts. This resource is typically referenced from the `crmi-softwaresystem` extension
Danger Signs - Central cyanosis Codes (Example) | Codes representing possible values for the Danger Signs - Central cyanosis element
Danger Signs - No danger signs Codes (Example) | Codes representing possible values for the Danger Signs - No danger signs element
Danger signs (Publishable Example) | Before each contact, the health worker should check whether the woman has any of the danger signs listed here – if yes, she should refer to the hospital urgently; if no, she should continue to the normal contact
Danger signs Codes (Example) | Codes representing possible values for the Danger signs element
Danger signs Codes Grouper (Computable Example) | Group Valueset with codes representing possible values for the Danger signs Codes Grouper element
Danger signs Codes Grouper (Expanded Example) | Group Valueset with codes representing possible values for the Danger signs Codes Grouper element
Danger signs Codes Grouper (Publishable Example) | Group Valueset with codes representing possible values for the Danger signs Codes Grouper element
Example Evaluation Result Parameters | Example Parameters resource demonstrating the use of data-absent-reason extension to indicate a null evaluation result.
Example Group Definition | Example Group Definition illustrating the use of an expression to define group membership.
Example Logic Library - Module Definition | This library is used as an example module definition in the FHIR Quality Measure Implementation Guide
Example MeasureReport | Example MeasureReport illustrating use of MeasureReport as a test case.
Example Medication Definition | Example of a Medication resource illustrating use as a definitional artifact.
Example MedicationKnowledge Definition | Example of a MedicationKnowledge resource illustrating use as a definitional artifact.
Example Publishable TerminologyCapabilities | Example Publishable Terminology Capabilities to describe an environment capable of expanding LOINC value sets, but not RxNORM value sets
Example Shareable TerminologyCapabilities | Example Shareable Terminology Capabilities to describe an environment capable of expanding LOINC value sets, but not RxNORM value sets
Example Substance Definition | Example of a Substance resource illustrating use as a definitional artifact.
Example TestCase Group | Example Group illustrating use of the cqf-testArtifact extension to build a set of test data for an artifact.
FHIR Common (Computable Example) | This library defines terminologies and functions commonly used in FHIR-based CQL artifacts.
FHIR Common (Example) | This library defines terminologies and functions commonly used in FHIR-based CQL artifacts.
FHIR Common (Executable Example) | This library defines terminologies and functions commonly used in FHIR-based CQL artifacts.
FHIR Common (Publishable Example) | This library defines terminologies and functions commonly used in FHIR-based CQL artifacts.
FHIR Common (Shareable Example) | This library defines terminologies and functions commonly used in FHIR-based CQL artifacts.
ImplementationGuide Example | This implementation guide demonstrates the use of the expansion parameters extension
Module Configuration Example Library for Recommendation 10 (Endpoint-specific prefetch configuration) | This library is used to populate the prefetch template for Recommendation 10 (Endpoint-specific)
Patient Example 1 | Example patient 1 in the test case group
Patient Example 2 | Example patient 2 in the test case group
Publishable ActivityDefinition Example | Example Publishable Activity Definition for a recommendation to order a medication
Publishable Capability Statement Example | Basic conformance statement for a Library Evaluation Service. A server can support more functionality than defined here, but this is the minimum amount
Publishable Concept Map Example | A mapping between the FHIR and HL7 v3 AddressUse Code systems
Publishable ImplementationGuide Example | This implementation guide demonstrates end-to-end capabilities for computable clinical practice guidelines following the World Health Organization SMART IG approach
Publishable OperationDefinition Example | Limited implementation of the Populate Questionnaire implementation
PublishableGraphDefinitionExample | Example of a Publishable GraphDefinition
PublishableSearchParameterExample | Search by resource identifier - e.g. same as the read interaction, but can return included resources
SNOMEDCTExample | SNOMED CT is a concept-based, scientifically validated terminology that provides a unique and permanent concept identifier that can be included in multiple HL7 data types including CD and CE. The concepts are managed to avoid “semantic drift” so the meaning remains constant. If the concept is found to be ambiguous or the meaning changes, the concept is inactivated but still retained and the identifier is never reused. SNOMED CT’s concepts are interrelated hierarchically and using description logic. SNOMED CT concepts have a unique “fully-specified name”, a preferred term, and, optionally, synonyms. The description languages include English and Spanish.
SNOMEDCTShareable | SNOMED CT is a concept-based, scientifically validated terminology that provides a unique and permanent concept identifier that can be included in multiple HL7 data types including CD and CE. The concepts are managed to avoid “semantic drift” so the meaning remains constant. If the concept is found to be ambiguous or the meaning changes, the concept is inactivated but still retained and the identifier is never reused. SNOMED CT’s concepts are interrelated hierarchically and using description logic. SNOMED CT concepts have a unique “fully-specified name”, a preferred term, and, optionally, synonyms. The description languages include English and Spanish.
Shareable ActivityDefinition Example | Example Shareable Activity Definition for a recommendation to order a medication
Shareable ActivityDefinition Example Artifact Reference | Example Shareable Activity Definition for a recommendation to order a medication. The medication uses the artifact-reference extension to a corresponding medication identified by artifact-url and artifact-version extensions
Shareable Capability Statement Example | Basic conformance statement for a Library Evaluation Service. A server can support more functionality than defined here, but this is the minimum amount
Shareable Concept Map Example | A mapping between the FHIR and HL7 v3 AddressUse Code systems
Shareable ImplementationGuide Example | This implementation guide demonstrates end-to-end capabilities for computable clinical practice guidelines following the World Health Organization SMART IG approach
Shareable OperationDefinition Example | Limited implementation of the Populate Questionnaire implementation
ShareableGraphDefinitionExample | Example of a Shareable GraphDefinition
ShareableSearchParameterExample | Search by resource identifier - e.g. same as the read interaction, but can return included resources
Specific health concern(s) (Shareable Example) | If the woman came to the facility with a specific health concern, select the health concern(s) from the list
Specific health concern(s) Codes (Shareable Example) | Codes representing possible values for the Specific health concern(s) element