5.17.0

Version 5.17.0 adds support for content profiles. Content profiles allow authors to indicate the fields and paths that should be marked as "Must Support". Future versions of content profiles will allow for additional features.

Currently, "must supports" is only reflected in exported FHIR profiles and extensions. Future versions will reflect "must support" in other artifacts (e.g., FHIR logical models, model-doc, and an upcoming data dictionary).

Each IG can have at most one content profile file. It is specified in the configuration JSON via a contentProfile property with the name of the file as its value. For example:

"contentProfile": "cp-mcode.txt",

The following demonstrates the correct format for a content profile file:

Grammar: ContentProfile 1.0

Namespace: shr.core
    Patient:
        Person.DateOfBirth MS
        Person.AdministrativeGender MS
        Person.Race MS
        Person.Ethnicity MS
        Person.Address.PostalCode MS
        Person.Deceased MS
    ComorbidCondition:
        PatientSubjectOfRecord MS
        Code MS
        ClinicalStatus MS
    // ... more ...

Namespace: oncocore
    CancerCondition:
        PatientSubjectOfRecord MS
        Code MS
        ClinicalStatus MS
        BodyLocation.LocationCode MS
        MorphologyBehavior MS
        DateOfDiagnosis MS
    // ... more ...