This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Publishing Package Artifact Definition

From HL7Wiki
Jump to navigation Jump to search

Return to Artifact List

Publishing Package - initial layout only

Alternate considerations:

  • Publication Package
  • Publishing Grouper
  • Publication Grouper

Definition and Purpose

NOTES:

package -

packageLocation@root values
  • "DEFN" The package represents the artifacts being defined.
  • "BAL" The package groups a set of content defined elsewhere intended to be submitted for ballot
    QUESTION:[why "elsewhere" why could not a ballot package have DEFN elements within a DEFN package that is part of its content??]
  • "PUB" The package a set of content defined elsewhere as a formal publication
    QUESTION:[why "elsewhere" why could not a publication package (like a Normative Edition) have DEFN elements within one or more DEFN package(s) that is(are) part of its content??]
contents:
freehand, DAM, domainInstanceExample, SB, DT model, IFC, vocModel, staticModel (SM) (serialized or flat), serialized (SM), derived (SM), strucDoc, TE, INT, AR, interactionProfile, conformanceProfile, testScenario, publication, package

QUESTION:Why is mif:publication/mif:packageLocation/@root not limited to "PUB" only?

MIF ballot:

  • says realmNamespace is "Mandatory",
    OBSERVATION: but it is optional in the schemas (at least in mif:package/packageLocation)
  • also says that packageLocation/@artifact - "Identifies the type of artifact represented. Applies to all "Definition" artifacts. The set of artifacts is controlled by HL7's Publishing work group in consultation with Modeling & Methodology and Tooling."
    OBSERVATION: Clearly, it does not apply to the DEFN file for CorePrinciples, because it is not a "DC" and therefore its package location is (I believe):
    <mif:packageLocation root="DEFN" realmNamespace="UV" name="v3modelcoreprinciples"/>

SAIF Matrix Location

Row(s)

  • Conceptual (CIM)
  • Logical (PIM)
  • Implementable (PSM)

Column(s)

  • Enterprise/Business
  • Information
  • Computational
  • Engineering
  • Technical

Audience

Health Care Community Audiences:

  • General public
  • Health care practitioners
  • Health system administrators
  • Health care policy makers

Health Care Information Technology (IT) Audiences:

  • System designers and architects
  • System purchasers
  • Programmers/implementers
  • System vendor management

Applicability

Text

Rationale: More text

Requirements, Relationships and Content

  1. Some requirement
    1. RationaleSome reason
  2. Some other requirement
    1. RationaleSome other reason

Relationships and traceability

  • Some relationship
    • Rationale: Reason for relationship
  • Some other relationship
    • Rationale: Reason for other relationship

Artifact types that may or must relate to this artifact types:

  • Many-related Artifact Type
  • Another Many-related Artifact Type

Content

  • Content element name - Brief Description
  • Another content element name - Brief Description
    • Sub-element name - Brief Description
  • Another content element name - Brief Description

Artifact Technology

Text here

Rationale

  • Some reason
  • Some other reason

Alternatives

Some technology

  • Some pro or con
  • Some other pro or con

Content Constraints

  1. Some rule
    1. Rationale: Some reason
  2. Some other rule
    1. Rationale: Some other reason

Content Guidelines

  1. Some rule
    1. Rationale: Some reason
  2. Some other rule
    1. Rationale: Some other reason

Publishing Representation(s)

  1. Some text
    1. Rationale: Some rationale
  2. Some other text
    1. Rationale: Some other rationale

Publishing Constraints

  1. Some rule
    1. Rationale: Some reason
  2. Some other rule
    1. Rationale: Some other reason

Tooling Considerations

  1. Nice-to-have|Required: Some feature
    1. Rationale: Some rationale
  2. Nice-to-have|Required: Some other feature
    1. Rationale: Some other rationale

Development Process Considerations

  1. Some text
    1. Rationale: Some rationale
  2. Some other text
    1. Rationale: Some other rationale

Governance Process Considerations

  1. Governance Process name - Some process description
    1. Rationale: Some rationale
  2. Another Governance Process name - Process description
    1. Rationale: Some other rationale

Issues

  • Some issue
  • Some other issue