0.0.1 - CI Build
SequoiaProjectHealthcareDirectoryImplementationGuideSTU3 - Local Development build (v0.0.1). See the Directory of published versions
A | B | C | D | |
---|---|---|---|---|
1 | Resource | Sequoia FHIR STU3 | Sequoia FHIR R4 change | Notes |
2 | Organization | description | Changed to "text" | There is no description field in Organization. Suggest using Organization.text if this is meant to be a human readable description. If not then a description extension would be required. Original: <description value="This is a organization description data element."/> R4 Compliant: <text> <status ="additional"/> <div xmlns="http://www.w3.org/1999/xhtml"> This is a organization description data element. </div> </text> |
3 | Organization | alias.value="" | Populate value attribute or remove element | Several examples had <alias value=""/>. This is not allowed in FHIR. If there is no alias for the Organization, then the element should be removed for that instance. Below it has been commented out. Original: <alias value=""/> R4 Compliant <!-- <alias value=""/> --> |
4 | Organization | contact.purpose | Moved content from value attribute to text element. | The purpose element is of type CodeableConcept with an extesible binding to http://hl7.org/fhir/valueset-contactentity-type.html. If a text string is going to be used instead of a code from that ValueSet, it needs to be in purpose.text. Original: <purpose value="Operations"/> R4 Compliant: <purpose> <text value="Operations"/> </purpose> |
5 | Organization | address.line | Populate value attribute or remove element | Several examples had <line value=""/>. This is not allowed in FHIR. If there is no line for an Address, then the element should be removed for that instance. Below it has been commented out. Original: <line value=""/> R4 Compliant: <!-- <line value=""/> --> |
6 | Organization | extension.url="OrgPosition" | Created a contained Location resource and an extension to reference it . | It is not legal to store a position element inside a coding.value. The Location resource is the proper way to represent GPS coordinates. Created a contained Location element and an OrgPosition extension to reference it. Original: <extension url="OrgPosition"> <valueCodeableConcept> <coding> <system value="https://sequoiaproject.org/StructureDefinition/Address/Position/1.0.0"/> <value> <position> <longitude value="-97.7047386"/> <latitude value="30.4159542"/> </position> </value> </coding> </valueCodeableConcept> </extension> R4 Compliant: <contained> <Location> <id value="orgloc"/> <position> <longitude value="-97.7047386"/> <latitude value="30.4159542"/> </position> </Location> </contained> ... <extension url="https://sequoiaproject.org/fhir/sphd-stu3/StructureDefinition/OrgLocation"> <valueReference> <reference value="#orgloc"/> </valueReference> </extension> |
7 | Organization | managingOrg | There is no managingOrg element on Organization. Use Endpoint.managingOrganization instead. | There is no managingOrg element on Organization. Use Endpoint.managingOrganization instead. |
8 | Organization | endpoint | Organization.endpoint was missing. Added reference. | The original example had a contained Endpoint resource, but no reference to it. Added Organization.endpoint with a reference to the contained resource. Original: R4 Compliant: <endpoint> <reference value="#7.7.7.7"/> </endpoint> |
9 | Endpoint | identifier.type.value="HCID" | A value attribute is not legal on this element, since it is a CodeableConcept. Moved HCID to coding.code and added system. | Created a CodeSystem resource (https://sequoiaproject.org/CodeSystem/sequoia-codes) for custom Sequoia project codes such as HCID. Updated example to be a valid CodeableConcept with HCID as the code from the sequoia-codes code system. Original: <type value="HCID"/> R4 Compliant: <type> <coding> <system value="https://sequoiaproject.org/CodeSystem/sequoia-codes"/> <code value="HCID"/> </coding> </type> |
10 | Endpoint | status | Added status.value="active" | Added status since it is a required element on Endpoint. Original: R4 Compliant: <status value="active"/> |
11 | <ANY> | name, type, address, extension, contained, part of, connectionType, payloadMimeType | Changed order of elements | Various elements were out of order. Changed order to match the order prescribed for the Organization resource: http://hl7.org/fhir/organization.html |
12 | <ANY> | system.value="http://www.hl7.org/oid/" | system.value="urn:ietf:rfc:3986" | In FHIR, OIDs must be represented in URI syntax, so the system must be "urn:ietf:rfc:3986" and the OID itself is represented as "urn:oid:X.X.X" where X.X.X is the OID. Original: <system value="http://www.hl7.org/oid/"/> <value value="7.7.7.7"/> R4 Compliant: <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:7.7.7.7"/> |
13 | <ANY> | code.value="" | Populate value attribute or remove element | Several examples had <code value=""/> . This is not allowed in FHIR. The code must be populated with a real code or the code element should be removed. It is commented out below. Original: <code value=""/> R4 Compliant: <!-- <code value=""/> --> |