Is it not the same URL as the read? (just different HTTP method)

POST https://healthshare.dev/csp/healthshare/fhiraccess/fhiraccess/Patient?_format=json&iscSessionId=0KbVHOguxHNv9ou7-xQLCxCsdcrcP9vOdxblRGOJ40c

Very empty patient (supposedly minimum required fields according to docs)

{
  "resourceType": "Patient",
  "identifier": [
    {
      "type": {
        "coding": [
          {
            "code": "MR",
            "display": "MR"
          }
        ],
        "text": "MR"
      },
      "system": "urn:oid:2.16.840.1.113883.4.1",
      "value": "200000007"
    }
  ],
  "active": true,
  "name": [
    {
      "use": "usual",
      "family": [
        "Doe"
      ],
      "given": [
        "John"
      ]
    }
  ],
  "gender": "male",
  "birthDate": "2000-09-01",
  "deceasedBoolean": false,
  "address": [
    {
      "use": "home"
    }
  ],
  "multipleBirthBoolean": false,
  "contact": [
    {
      "relationship": [
        {
          "coding": [
            {
              "system": "http://hl7.org/fhir/patient-contact-relationship",
              "code": "friend",
              "display": "Friend"
            }
          ],
          "text": "Friend"
        }
      ],
      "name": {
        "use": "usual",
        "text": "Frouwina Jong",
        "family": [
          "Jong"
        ],
        "given": [
          "Frouwina"
        ]
      },
      "telecom": [
        {
          "system": "phone",
          "value": "289-990-5494",
          "use": "home"
        }
      ],
      "address": {
        "line": [
          "1173 Oak Drive"
        ],
        "city": "Chicago",
        "state": "DE",
        "postalCode": "30732",
        "country": "USA"
      },
      "gender": "female"
    }
  ],
  "communication": [
    {
      "language": {
        "coding": [
          {
            "code": "en",
            "display": "English"
          }
        ],
        "text": "English"
      },
      "preferred": true
    }
  ]
}

That's what I figured and have done. Reading has an ID in the path (GET request) and creating does not (POST request). Standard RESTful API stuff more or less. Strange.

No, that's just our messed up installation (whoever configured it on our end). I thought that at first too. The application name is "fhiraccess" as well, or service path or whatever its technically called, which makes it very confusing. Again, reads work (and for the sake of being thorough I've already tried it both ways).

Sure, the full version string is: Cache for UNIX (Red Hat Enterprise Linux for x86-64) 2017.1.1 (Build 111_0_17521U) Wed Jul 26 2017 13:00:54 EDT [HealthShare Modules:Core:15.03.8382 + Linkage Engine:15.03.8382 + Patient Index:15.03.8382 + Clinical Viewer:15.03.8382 + Active Analytics:15.03.8382]

What you said seems to make sense about the FHIR Gateway. I can read just fine, but writing seems to be the issue. That's a shame data can't be written that way. There are a variety of mock data generation tools that I'm working with but they all operate with FHIR. So getting this data into HealthShare is problematic. Any ideas on going from FHIR into HealthShare? In Bulk?

Thanks. I was able to convert the FHIR JSON to CCDA (more or less). It may work for my needs, but if not, I may try something like this.