Merge pull request #224 from FHIR/profiling

Add a minimal ShareableViewDefinition profile.

input/fsh/models.fsh

@@ -30,14 +30,13 @@ criteria are defined by FHIRPath expressions.
   Name of the view definition, must be in a database-friendly format.
 """
 * name obeys sql-name
-* version 0..1 string "Business version of the view definition"
 * title 0..1 string "Name for this view definition (human friendly)" """
   A optional human-readable description of the view.
 """
+* meta 0..1 Meta "Metadata about the view definition"
 * status 1..1 code "draft | active | retired | unknown"
 * status from http://hl7.org/fhir/ValueSet/publication-status
 * experimental 0..1 boolean "For testing purposes, not real usage"
-* date 0..1 dateTime "Date last changed"
 * publisher 0..1 string "Name of the publisher/steward (organization or individual)"
 * contact 0..* ContactDetail "Contact details for the publisher"
 * description 0..1 markdown "Natural language description of the view definition"

input/fsh/profiles.fsh

@@ -0,0 +1,7 @@
+Profile: ShareableViewDefinition
+Parent: ViewDefinition
+Description: "A Shareable View Definition"
+* url 1..1
+* name 1..1
+* fhirVersion 1..*
+* select.column.type 1..1

input/pagecontent/StructureDefinition-ShareableViewDefinition-intro.md

@@ -0,0 +1,3 @@
+A profile of [View Definition](StructureDefinition-ViewDefinition.html) for views that are intended
+to be shared across organizations. It adds constraints to the base definition, such as requiring a URL, name, and types for each
+column. See the differential table below for details.

input/pagecontent/StructureDefinition-ViewDefinition-intro.md

@@ -30,3 +30,7 @@ A system-specific *view runner* implementation can execute a *view definition* a
 return the results as a table that can easily be used in the user's tech stack. See the
 [system layers](index.html#system-layers) for details.
 
+## Profiling
+ViewDefinitions may be profiled to meet specific needs. For instance, the [ShareableViewDefinition](StructureDefinition-ShareableViewDefinition.html) profile
+adds constraints for view definitions intended to be shared between systems. Implementers may create their
+own ViewDefinition profiles for further specialized needs.

sushi-config.yaml

@@ -74,6 +74,7 @@ menu:
   Purpose: purpose.html
   View Definition: StructureDefinition-ViewDefinition.html
   Implementer Guidance: implementer_guidance.html
+  Artifacts: artifacts.html
   Contributing: contributing.html
 
 # ╭───────────────────────────Less Common Implementation Guide Properties──────────────────────────╮