As the GitHub Issue described, Server implementation only need to support either DocumentReference.content.attachment.data or DocumentReference.content.attachment.url
Because the invariant us-core-6 guarantees that each DocumentReference has either content.attachment.data or content.attachment.url, there is no need to have an explicit Must support check for these two elements.
New behavior
DocumentReference.content.attachment.data or DocumentReference.content.attachment.url are must supports
Summary
This PR fixes GitHub Issue #316
As the GitHub Issue described, Server implementation only need to support either DocumentReference.content.attachment.data or DocumentReference.content.attachment.url
Because the invariant us-core-6 guarantees that each DocumentReference has either content.attachment.data or content.attachment.url, there is no need to have an explicit Must support check for these two elements.
New behavior
DocumentReference.content.attachment.data or DocumentReference.content.attachment.url are must supports
Code changes
Updated metadata_extractor and uscore_geneator
Testing guidance